Traces: Move towards using OTEL naming conventions #51379
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
joey-grafana
changed the title
|
Drone build failed: https://drone.grafana.net/grafana/grafana-enterprise/23978 |
|
Drone build failed: https://drone.grafana.net/grafana/grafana-enterprise/24444 |
|
Drone build failed: https://drone.grafana.net/grafana/grafana-enterprise/24446 |
connorlindsey
approved these changes
Jul 5, 2022
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.
What this PR does / why we need it:
This PR moves us towards using OTEL terminology in our Traces.
Resource is what OTEL use to specify what we call a process. Similarly, OTEL uses attributes where we use tags and events where we use logs.
Which issue(s) this PR fixes:
Fixes #51378
Special notes for your reviewer: