Closed FelipeEmerim closed 1 year ago
We can open a Pull Request containing the fix but before doing so we would like to confirm if this is actually a bug or if we are missing something.
I don't think you're missing anything. A PR would be appreciated.
What happened?
Exporting error spans to Zipkin results in a 400 error because zipkin cannot parse the annotations timestamp value.
Steps to Reproduce
We can reliably reproduce this using otel-collector zipkin receiver and forcing an http span to throw an error.
Expected Result
We expected the span to be exported correctly
Actual Result
The spans are not exported because of a 400 error.
Additional Details
This error was partially fixed in 1.16, but we believe the rounding should also be applied in the
_toZipkinAnnotations
function of the zipkin exporter. We can open a Pull Request containing the fix but before doing so we would like to confirm if this is actually a bug or if we are missing something.OpenTelemetry Setup Code
package.json
Relevant log output