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
As a followup to #2487, I would like to be able to pad trace IDs with leading 0s.
Problem
Given a traceparent header like 00-00000000000000001b3ef83a5d15ed1b-61409d351b3a5d99-01, jaeger will store (and thus display + interpolate) the trace ID as 1b3ef83a5d15ed1b. When attempting to use the shortened trace ID to link to logs some tracing integrations (in my case, logs using pino instrumented with the OpenTelemetry pino instrumentation) will use the full length trace ID, making jaeger link patterns not work.
Proposal
The syntax for this could look like #{traceID | pad_start 32 0}
Open questions
No response
The text was updated successfully, but these errors were encountered:
Requirement
As a followup to #2487, I would like to be able to pad trace IDs with leading 0s.
Problem
Given a traceparent header like 00-00000000000000001b3ef83a5d15ed1b-61409d351b3a5d99-01, jaeger will store (and thus display + interpolate) the trace ID as 1b3ef83a5d15ed1b. When attempting to use the shortened trace ID to link to logs some tracing integrations (in my case, logs using pino instrumented with the OpenTelemetry pino instrumentation) will use the full length trace ID, making jaeger link patterns not work.
Proposal
The syntax for this could look like
#{traceID | pad_start 32 0}
Open questions
No response
The text was updated successfully, but these errors were encountered: