-
Notifications
You must be signed in to change notification settings - Fork 652
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 status to the tags for the Zipkin Exporter #1124
Add status to the tags for the Zipkin Exporter #1124
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.
The PR looks pretty good. It would be great to add a test that confirms the status and description is set when the span status is set to a different value.
Please add a note to the changelog as well! |
…tatus description for Zipkin exporter
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.
Thanks for addressing my comments! Looks like you'll need to update the branch before we can merge it.
Looks like its out of date once again |
@@ -183,6 +183,15 @@ def _translate_to_zipkin(self, spans: Sequence[Span]): | |||
"otel.instrumentation_library.version" | |||
] = span.instrumentation_info.version | |||
|
|||
if span.status is not None: | |||
zipkin_span["tags"][ | |||
"ot.status_code" |
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.
Hey there - these tags don't quite look correct because they're ot
. The referenced spec was added several months ago (open-telemetry/opentelemetry-specification#380) before the acronym was officially finalized as otel
. I have sent open-telemetry/opentelemetry-specification#967 to fix this.
I'd recommend either proactively using otel
(it's pretty obvious that's what it should be, see lines 180 / 183 in this file) or waiting a bit if you'd like to see the update in the spec merged. As it stands, if this merges it'll need to be updated right away anyways.
@wilguo Also as general advice, it would be great if the PR title has more concrete information about the actual change, rather than being too generic. For example, |
Sorry @anuraaga, I may have prematurely merged this after seeing it had enough approvals previously. If there are any leftover issues, can you open separate issues to track them? |
The merge looks fine since it was updated to use the new (approved but not quite merged) prefixes :) |
…-telemetry#1124) * [Issue open-telemetry#1111] Add span status to tags for Zipkin exporter
Description
This PR adds status to the tags for the Zipkin Exporter, closing #1111.
The changes have been made following these specifications:
https://github.com/open-telemetry/opentelemetry-specification/blob/master/specification/trace/sdk_exporters/zipkin.md#status
Fixes #1111
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Ran test file for Zipkin Exporter
tox -e py38-test-exporter-zipkin
Checklist: