-
Notifications
You must be signed in to change notification settings - Fork 97
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
feat: extract decision span from full span #1338
Conversation
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.
I think this mostly makes sense, but would like to see the rename of AnnotationType to SpanType moved into a separate PR to help make this one a little more concise.
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.
Looks good, thanks @VinozzZ
Extract only necessary information that's needed for trace decision from a full span so that we can forward only the key fields to peers later part of #1318 - add a method on `Span` to extract only necessary information into a new types.Event - add a method to differentiate a full span from a decision span - store `IsRoot` information on `Span` - simplify naming for span annotation types
Which problem is this PR solving?
Extract only necessary information that's needed for trace decision from a full span so that we can forward only the key fields to peers later
part of #1318
Short description of the changes
Span
to extract only necessary information into a new types.EventIsRoot
information onSpan