-
Notifications
You must be signed in to change notification settings - Fork 94
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(otlp): infer span category from attributes (#4509)
Relay assigns a `category` to incoming spans based on their `op` (see [our docs](https://develop.sentry.dev/sdk/telemetry/traces/span-operations/#list-of-operations) for possible category values). Unlike Sentry's `op` field, OTel span names aren't structured and therefore can't be used to determine the span `category`. In order to support categorizing incoming OTel spans, update the span categorization algorithm to: 1. Use the incoming `sentry.category` attribute directly if given. This allows our SDKs to be explicit about the intended category and also lets users explicitly perform categorization in case our automatic categorization is ever incorrect. 2. Extract the category from `op`. This is what we do today, and will keep categorization consistent for Sentry SDK clients sending spans via transaction events now and in the future. 3. When `op` is missing (e.g. an OTLP span), infer the category based on the span's attributes. This will categorize incoming OTel spans based on semantic conventions. Currently the inference only supports the five categories we use in the transaction summary page's operation filter, which is the page the Performance team is currently migrating to EAP. We'll expand it in the future as we move more of the product surface area over to support EAP/span-first/OTLP.
- Loading branch information
Showing
5 changed files
with
181 additions
and
24 deletions.
There are no files selected for viewing
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
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
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
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
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