-
Notifications
You must be signed in to change notification settings - Fork 862
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
Azcore separate tracer #23715
base: main
Are you sure you want to change the base?
Azcore separate tracer #23715
Conversation
to allow azcore consumers to indicate the azcore tracer should be named after the azcore module instead of the consumer's module
Thank you for your contribution @kjg! We will review the pull request and get back to you soon. |
I'm not sure how to make the dependency check pass since I can't update tracing/azotel version of azcore and account for the breaking change until the change is merged and a new version released. Any guidance on how to approach that? |
Hi @kjg. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
I'd love to keep working on this if I can get some guidance. Thanks! |
Fixes [Tracing] Allow Client libraries to configure schema URL #23307
This PR allows a schemaURL to be passed to the NewTracer function so that consumers can create tracers that use a different schemaURL than azcore.
It updates azcore to use the otel semconv package that sets a schemaURL and then uses the semconv Constances for the span keys that have defined semconv keys.
This PR also adds a
WithCoreTracerName
function to the azcore client so the consumers that do want to do custom tracing can make azcore using azcore's module name and version for the HTTP tracing, and their own module name and version for their portion of the tracing. UsingWithCoreTracerName
only changes the values used for tracing to azcore values, it still leaves the passed in module name and version for use with the HTTP User Agent header.I chose this approach because it looks like many of the consumers of this client