-
Notifications
You must be signed in to change notification settings - Fork 576
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
Prepare for v0.7.0 release of contrib #103
Conversation
a8bfd7e
to
daa2b9b
Compare
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.
Did we want to remove the internal/trace
functionality that was moved to the main repo's api/standard
package? Or, should that be a separate PR?
I up a separate PR, though it's based on this one so it should be reviewed and merged after this one lands. |
Yes, I was planning a separate PR. There's also at least one other separate PR for the use of semantic tag names that have now shuffled off into the main Otel repo. |
Co-authored-by: Tyler Yahn <MrAlias@users.noreply.github.com>
It was printing an ID of the created span instead. Also drop the if clause checking if span has a parent span ID - we know at this point that the condition is always true.
This upgrades the dependency on
go.opentelemetry.io/otel
to the just-released v0.7.0 and fixes API changes causing breakage in the metric exporters.