-
Notifications
You must be signed in to change notification settings - Fork 7
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
add extensions to otel.trace #77
base: main
Are you sure you want to change the base?
Conversation
val to_span_link : | ||
?trace_state:string -> | ||
?attrs:key_value list -> | ||
?dropped_attributes_count:int -> | ||
t -> | ||
Span_link.t | ||
(** Turn the scope into a span link *) |
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'm currently doing the following in a codebase to get the span_link
scope |> Scope.to_span_ctx |> Span_link.of_span_ctx
Is the Span_link.of_span_ctx
still required now that we can go directly from scope
to span_link
?
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.
And if yes, should we add ?dropped_attributes_count:int
to the Span_link.of_span_ctx
to be consistent ?
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 we can keep both, but yes, adding the optional arguments is good for consistency.
a83464b
to
e789462
Compare
Span_kind.t
, add {kind,set_kind} toScope