-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(spans): Handle span schema v1 from Relay #57284
Merged
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
github-actions
bot
added
the
Scope: Backend
Automatically applied to PRs that change backend components
label
Oct 2, 2023
nikhars
approved these changes
Oct 2, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall looks good to me. Left a comment for clarification.
Zylphrex
approved these changes
Oct 3, 2023
jjbayer
added a commit
to getsentry/relay
that referenced
this pull request
Oct 4, 2023
This PR makes the following changes to the relay -> sentry kafka schema for spans: * [breaking change] Encode the payload as JSON, not msgpack. Msgpack should only be used for payloads that contain (partial) binary data. * Add the fields `organization_id` and `retention_days` so the consumer does not have to look them up. * [through #2555] New field `span.sentry_tags` can be used instead of `span.data`. It now contains the same keys as expected by snuba. The values are guaranteed to be strings. * Some extra validation to make sure we do not send corrupted data. Sentry counterpart: getsentry/sentry#57284
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Related to getsentry/relay#2556