Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[Feature]: Add pad start formatting function #2505

Closed
drewcorlin1 opened this issue Nov 30, 2024 · 0 comments · Fixed by #2504
Closed

[Feature]: Add pad start formatting function #2505

drewcorlin1 opened this issue Nov 30, 2024 · 0 comments · Fixed by #2504

Comments

@drewcorlin1
Copy link
Contributor

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

# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant