[dougqh]

What Does This Do

Rebuilds the tracer-wide span tags (mergedTracerTags) when remote config enables or disables Data Streams Monitoring, not only when the tracing tags change.

Motivation

ConfigSnapshot reuses the previous snapshot's mergedTracerTags whenever the tracing tags are unchanged. But withTracerTags also reads isDataStreamsEnabled() to set or remove _dd.dsm.enabled. So an RC update that changes only data_streams_enabled (TracingConfigPoller) left _dd.dsm.enabled stale on every new span:

• DSM enabled through RC: the tag stays missing;
• DSM disabled through RC: the tag stays set.

The tag only corrected itself once some later RC update also changed the tracing tags.

Fix: also compare isDataStreamsEnabled() in the reuse check. It only runs when a snapshot is built (on RC updates), never per span.

Additional Notes

• CoreTracerTest.remoteConfigDataStreamsToggleUpdatesTracerTags fails on master (expected: <1> but was: <null> after RC enables DSM) and passes with the fix.
• Full dd-trace-core locally: the only failures were two Docker-based tests (no Docker locally) and two timing tests (DDAgentWriterCombinedTest, PendingTraceBufferTest). Both timing tests pass when rerun on their own.
• Found by /perf-review on Keep global tags apart from span defaults in the config snapshot (OTLP trace/resource-level split) #12937. It touches the same ConfigSnapshot block, so whichever lands second needs a small rebase.

Jira ticket: [PROJ-IDENT]

🤖 Generated with Claude Code

[datadog-prod-us1-3]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 61.43% (+1.57%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: e4ee5d3 | Docs | Give us feedback!}

[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.67 s	14.69 s	[-1.1%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	13.57 s	13.66 s	[-1.3%; +0.0%] (no difference)
startup:petclinic:appsec:Agent	17.73 s	17.55 s	[-0.1%; +2.2%] (no difference)
startup:petclinic:iast:Agent	17.55 s	17.58 s	[-0.9%; +0.6%] (no difference)
startup:petclinic:profiling:Agent	17.33 s	17.51 s	[-2.2%; +0.1%] (no difference)
startup:petclinic:sca:Agent	17.67 s	17.56 s	[-0.3%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	16.64 s	16.73 s	[-1.5%; +0.4%] (no difference)

Commit: e4ee5d38 · 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-19T21:13:17.182143Z	3b8dd31	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-prod-us1-3]

More details

The cache-reuse guard now accounts for DSM enablement, allowing remote-config updates to add or remove _dd.dsm.enabled even when tracing tags remain unchanged. The completed static review identified no reportable defects.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit 3b8dd31}

[mcculls]

Nice catch

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-21 12:02:57 UTC ℹ️ Start processing command /merge

---

2026-10-21 12:03:01 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-10-21 12:54:35 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for 76410f9:

• test_inst: [semeru8, 5/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-21 18:14:39 UTC ℹ️ Start processing command /merge

---

2026-10-21 18:14:43 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-10-21 19:28:07 UTC ℹ️ MergeQueue: This merge request was merged