-
Notifications
You must be signed in to change notification settings - Fork 5
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
Metadata about instrumented component — library name, version #5
Comments
So, to clarify, this would be potentially distinct for each span? Not just at initialization time? |
I, huh. That's a good question. On the one hand, path of least resistance — easy to 'open up' later, hard to 'close down'; that implies use the more restrictive "call a separate function" API? … but on the other hand, currently, libraries don't need to do any initialization. They can just straight-up call So, I guess, optional arguments to let with_span = Trace.with_span ~producer_name:"Mylib" ~producer_version:"1.0.3"
with_span ... |
It also depends on who uses that information. In theory, |
Okay, I've started to take the "standard k/v pair for the I'm using The patch here, if we want to go in that direction, would be:
|
Need to add an API entrypoint for libraries to self-report what is producing traces — in OpenTelemetry, this is called 'instrumentation scope.'
Need to add a collector-agnostic method to report this — I do like OTel's format, which is a tuple of
(name:string, version:string)
.The text was updated successfully, but these errors were encountered: