Use OTEL scopes better, especially instead of tags #420
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
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #420 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 130 130
Lines 9496 9501 +5
Branches 1227 1227
=========================================
+ Hits 9496 9501 +5 ☔ View full report in Codecov by Sentry. |
Deploying logfire-docs with
|
| Latest commit: |
9472d2f
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://ee2bbe11.logfire-docs.pages.dev |
| Branch Preview URL: | https://alex-scopes.logfire-docs.pages.dev |
Kludex
approved these changes
Sep 12, 2024
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.
The OTEL instrumentation scope is a useful concept and we should use it consistently when it's appropriate. This way queries like
GROUP BY otel_scope_namewill work better for breaking down where spans are coming from.