Refactor span tag processing API

[PerfectSlayer]

What Does This Do

This PR replaces the four CoreSpan.processTagsAndBaggage* variants with a single method taking an int of options:

void processTagsAndBaggage(MetadataConsumer consumer, int options);

Option	Meaning
STRUCTURED_LINKS	The protocol encodes span links natively, so they are not added as the _dd.span_links tag
STRUCTURED_EVENTS	The protocol encodes span events natively, so they are not added as the events tag
OWN_PROPAGATION_TAGS	Serializes the span context's own propagation tags (the default option)
ROOT_PROPAGATION_TAGS	Serializes the local root span context's propagation tags, as for the first span of a chunk

Motivation

Simplify API and make it more explicit:

• DDSpan had 4 overrides and DDSpanContext 5 methods, built from combinations of booleans. Each new serialization need meant two more overloads. They are now a single method each.
• Each call site now states what its protocol needs, instead of depending on which variant it picks and on how the interface defaults delegate to each other.
• Test spans (PojoSpan, SimpleSpan, CountingPojoSpan) override a single method.

Additional Notes

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

Jira ticket: [PROJ-IDENT]

🤖 Generated with Claude Code

[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-09T08:57:15.092647Z	87e65c0	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-09T08:59:29.158073Z	87e65c0	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.

[datadog-official]

More details

The migrated serializers preserve first-in-chunk root propagation tags, per-span propagation tags where previously used, and existing link, event, and baggage handling.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 87e65c0 · @DataDog review to ask questions}

[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	13.93 s	13.90 s	[-0.4%; +0.9%] (no difference)
startup:insecure-bank:tracing:Agent	12.86 s	12.98 s	[-1.6%; -0.2%] (maybe better)
startup:petclinic:appsec:Agent	17.13 s	16.47 s	[-0.6%; +8.5%] (no difference)
startup:petclinic:iast:Agent	16.48 s	16.92 s	[-6.9%; +1.7%] (no difference)
startup:petclinic:profiling:Agent	16.55 s	16.91 s	[-3.3%; -1.0%] (maybe better)
startup:petclinic:sca:Agent	17.10 s	16.94 s	[-0.1%; +1.9%] (no difference)
startup:petclinic:tracing:Agent	16.07 s	16.13 s	[-1.6%; +0.7%] (no difference)

Commit: 3bf09db8 · 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.

[datadog-official]

More details

The serializer options preserve existing link, event, and baggage handling, including root propagation tags on the first span of each chunk and own propagation tags for independent serialization.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 4042930}

[PerfectSlayer]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-12 17:24:55 UTC ℹ️ Start processing command /merge

---

2026-10-12 17:25:01 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

• Run /code blockers to see what is blocking it.
• Run /remove to cancel it.

---

2026-10-12 18:32:18 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in master is approximately 1h (p90).

---

2026-10-12 19:45:20 UTC ℹ️ MergeQueue: This merge request was merged

[datadog-official]

More details

The new option flags preserve the previous propagation-tag choices at serialization call sites. Validation was limited to static analysis; tests and production behavior were not exercised.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 4042930}