feat(otlp): Use OTel-friendly default Explore fields #93736
+72
−11
Conversation
This file contains hidden or 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
Also update `status`, since it can now apply to a span.
github-actions
bot
added
the
Scope: Frontend
This comment was marked as outdated.
This comment was marked as outdated.
Zylphrex
approved these changes
Jun 18, 2025
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.
If the OTel-friendly UI flag is on, change the default fields for Explore to ID, Name, Duration, and Timestamp. We are moving away from OP and Description. Is waiting for #93725 to add backend support
I added field definitions to
FieldKeys, since thisnameandkindareSpanV2fields, that are EAP-specific an the most recent.I also updated the type of span definitions to
Record<string, FieldDefinition>since span fields are set by the user, so we'll never have a complete listing to definitions.