-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(core/spans): Add span v2 and envelope type definitions #19100
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
Open
Lms24
wants to merge
5
commits into
lms/feat-span-first
Choose a base branch
from
lms/span-first-pr1-spanv2-types
base: lms/feat-span-first
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
9fa2fd7
feat(core): Add SpanV2JSON and envelope type definitions
Lms24 d8bde46
rework intermediate representation
Lms24 fd5bfa7
fix SerializedSpanContainer
Lms24 b89549d
you're absolutely right
Lms24 a2215c6
Apply suggestion from @Lms24
Lms24 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
Oops, something went wrong.
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.
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.
l/q: Before we merge it as
SpanV2JSON. IsSpanV2the official term? Not sure how other SDKs will handle this, but maybe we could verify that before we get into future confusion what the difference between "span v2" and "span streaming" isThere 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.
Yeah I agree that
SpanV2JSONis not the ideal name here 😅SpanJSONwould be ideal but that's already taken. Reusing this is IMHO not really possible because it still features properties likedescription,measurements,data, etc. All those properties and concepts have no place in the new v2 span protocol.There's no official term for this intermediate step, as most SDKs besides JS never had a reason to surface serialized spans before. They just expose the regular span class instance to users. But we can't do that because OTel span instances are no longer writable at the point where they reach beforeSendSpan.
The old transaction based pattern basically was:
Span->SpanJSON-> sent asTransactionevent envelopeNow we need some other kind of intermediate name. Something like
Span->StreamedSpanJSON-> sent asSerializedSpanarray envelopeThe alternative here would be to directly convert the
Spanto aSerializedSpanand let users deal with the complicated attribute type. This has however the consequence that they could set atypethat doesn't conform with thevalueproperty of the attribute. Which is why I figured I'd prefer keeping the intermediate step.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.
The good news here is, as long as we merge against the epic branch, we can break as much as we want with the names 😅
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.
Cool. Thanks - overall SpanV2 is fine, I just wanted to challenge it once more