You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But if I use the Zipkin Exporter, these resource attributes are missing. I think this is because OtelToZipkinSpanTransformer does not add them to the span as tags. According to the docs these values are mandatory for the SDK so I think the Zipkin Exporter should not just drop them.
Steps to reproduce
Send some spans using the Zipkin Exporter.
What did you expect to see?
The mandatory resource attributes should be added to Zipkin spans as tags.
What did you see instead?
Those tags are missing.
What version and what artifacts are you using?
Artifacts: opentelemetry-sdk, opentelemetry-exporter-zipkin
Version: 1.27.0
How did you reference these artifacts?
Shouldn't it tough? I would assume this hasn't been specced yet but since the spec you linked seems stable, I'm questioning this assumption. Are there intentions to fix this?
Since the docs are saying that these values are mandatory for the SDK, I think the Zipkin Exporter should not drop them.
Describe the bug
If I use the Jaeger Exporter, I see the following resource attributes on spans:
But if I use the Zipkin Exporter, these resource attributes are missing. I think this is because
OtelToZipkinSpanTransformer
does not add them to the span as tags. According to the docs these values are mandatory for the SDK so I think the Zipkin Exporter should not just drop them.Steps to reproduce
Send some spans using the Zipkin Exporter.
What did you expect to see?
The mandatory resource attributes should be added to Zipkin spans as tags.
What did you see instead?
Those tags are missing.
What version and what artifacts are you using?
Artifacts:
opentelemetry-sdk
,opentelemetry-exporter-zipkin
Version:
1.27.0
How did you reference these artifacts?
Environment
Java:
liberica-17.0.7+7
OS: Mac OS 13.4.1
Additional context
N/A
The text was updated successfully, but these errors were encountered: