[PerfectSlayer]

What Does This Do

This PR simplifies #12739 (not yet released) while keeping its goal: malformed x-datadog-trace-id / x-datadog-parent-id headers no longer produce telemetry log events.

Motivation

#12739 cut the telemetry events (and Error Tracking volume) caused by malformed Datadog id headers, but it did so by:

• adding a public, "internal only" method to DD64bTraceId that nothing stops users from calling, and that DD128bTraceId and DDSpanId don't have;
• adding a second decimal parser next to the existing one;
• having the header decoding call these internal methods instead of the usual from methods.

The telemetry cost comes from logging the exception, not from throwing it. Handling NumberFormatException separately in the existing catch block is enough to remove it.

Additional Notes

• Trade-off: a malformed id still costs a thrown exception per request. Parse Datadog trace and span id headers without exceptions #12739's benchmark measured about 840-880 ns for an invalid id, against 21-43 ns without the exception, and about 40 ns more per extraction for valid ids. We accept that cost for invalid input coming from the network, in exchange for a smaller API and less code.
• Wider exclusion: the new catch also covers a malformed x-datadog-sampling-priority (Integer.parseInt). That is caller input too, so it is also kept out of telemetry.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

🤖 Generated with Claude Code

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.91 s	[-0.2%; +1.5%] (no difference)
startup:insecure-bank:tracing:Agent	12.77 s	12.97 s	[-2.4%; -0.7%] (maybe better)
startup:petclinic:appsec:Agent	17.05 s	16.85 s	[+0.4%; +2.0%] (maybe worse)
startup:petclinic:iast:Agent	16.78 s	17.02 s	[-2.2%; -0.6%] (maybe better)
startup:petclinic:profiling:Agent	16.76 s	16.70 s	[-0.8%; +1.5%] (no difference)
startup:petclinic:sca:Agent	17.03 s	16.82 s	[+0.4%; +2.1%] (maybe worse)
startup:petclinic:tracing:Agent	16.02 s	16.17 s	[-1.7%; -0.1%] (maybe better)

Commit: adc82087 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-19T11:12:37.947313Z	86e545d	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-19T11:15:36.515241Z	86e545d	Draft marked ready

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 86e545dd2b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[datadog-datadog-prod-us1-2]

Some out-of-range 20-digit trace and parent IDs are now accepted as wrapped 64-bit values, bypassing malformed-context rejection.

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 86e545d}

[mcculls]

This simplification makes sense to me

[PerfectSlayer]

Applied feedback and relabeled as bug fix due to the agentic review increasing the scope of the PR