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
The error tag is cleared and since our Error code is the pdata.StatusOk value the span ultimately will not be counted as an error (there are also errors in the collector receiver based on this).
The text was updated successfully, but these errors were encountered:
Just a heads up from after our conversation in the SIG meeting. We were planning to release about 20 hours from this being posted. Seeing as we have multiple approvals, and it is a bug I can understand allowing us to merge sooner, but I would like to point out that we are doing so.
Description
The Jaeger exporter translates a span status to an integer tag.
opentelemetry-go/exporters/jaeger/jaeger.go
Line 150 in b177541
The OpenTelemetry specification states this should be a string tag with the value of
OK
orERROR
.This can cause error spans to be translated to OK in the collector: https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/3de607f6cd38673924397f8a3c9158d89b491207/pkg/translator/jaeger/jaegerproto_to_traces.go#L211-L233
The
error
tag is cleared and since ourError
code is thepdata.StatusOk
value the span ultimately will not be counted as an error (there are also errors in the collector receiver based on this).The text was updated successfully, but these errors were encountered: