feat(spans): Track when each span was received #2688
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nikhars
approved these changes
Nov 3, 2023
phacops
force-pushed
the
pierre/spans-add-received-field
branch
6 times, most recently
from
48cabe0
to
7c2a3e8
Compare
phacops
force-pushed
the
pierre/spans-add-received-field
branch
from
7c2a3e8
to
3297407
Compare
jjbayer
approved these changes
Nov 6, 2023
Co-authored-by: Joris Bayer <joris.bayer@sentry.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In order to track the end to end latency of span ingestion, we need the time when the span was received by Relay.
Related PRs, in order they should merged in: