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
When the logs do not contain trace ID and span ID, the DataDog Go mapping spams the output with failed to decode trace id and failed to decode span id.
I tracked the problem down to the otel* variables, which has default "0":
When the logs do not contain trace ID and span ID, the DataDog Go mapping spams the output with
failed to decode trace id
andfailed to decode span id
.I tracked the problem down to the otel* variables, which has default "0":
This is decoded like a span ID/trace ID, so the 16 and 32 characters length check of the parser fails:
opentelemetry-mapping-go/pkg/otlp/logs/transform.go
Lines 92 to 93 in 70cee9d
opentelemetry-mapping-go/pkg/otlp/logs/transform.go
Lines 104 to 105 in 70cee9d
And the decoding:
opentelemetry-mapping-go/pkg/otlp/logs/transform.go
Lines 226 to 236 in 70cee9d
opentelemetry-mapping-go/pkg/otlp/logs/transform.go
Lines 238 to 248 in 70cee9d
The text was updated successfully, but these errors were encountered: