-
Notifications
You must be signed in to change notification settings - Fork 94
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
fix(spans): Normalize INP spans further #4298
Conversation
INP spans sets some top level span attributes inside span.data so make sure to pull them out to the top level. This has implications in the snuba consumer so that we do not redundant keys with slightly different names in span.data.
// INP spans sets some top level span attributes inside span.data so make sure to pull | ||
// them out to the top level before further processing. | ||
if let Annotated(Some(ref mut data), _) = span.data { | ||
if let Some(exclusive_time) = match data.other.get("sentry.exclusive_time") { |
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.
Could you add sentry.exclusive_time
and profile_id
as fields on the SpanData
type? I assume a hypothetical SDK that can only send Otel spans would still send these as span attributes? Or are these legacy fields that future SDKs should not send?
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.
They can continue sending them as span attributes.
INP spans sets some top level span attributes inside span.data so make sure to pull them out to the top level. This has implications in the snuba consumer so that we do not redundant keys with slightly different names in span.data.