[watson]

Summary

The debugger team agreed that every tracer reports its debugger metrics in a shared debugger instrumentation telemetry namespace instead of live_debugger.

 // DebuggerMetricCollector.DebuggerMetric (events.skipped, events.dropped)
-private static final String NAMESPACE = "live_debugger";
+private static final String NAMESPACE = "debugger";

The intake allows the new namespace since ddoghq/dd-go#23524. DataDog/system-tests#8052 adds a cross-tracer test for it.

Evidence

• Before: DebuggerMetricCollectorTest asserts metric.namespace == "live_debugger".
  After: it asserts metric.namespace == "debugger". I couldn't run the Gradle build locally, so CI is the first run.

Merge Danger

Door: two-way

Blast Radius: internal

Only internal telemetry changes. The intake change (ddoghq/dd-go#23524) is merged; it must be deployed before a release containing this ships, because until then the intake rejects generate-metrics payloads that contain debugger series.

Jira ticket: DEBUG-6335

🤖 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-15T16:07:54.047266Z	cbbd732	Draft marked ready
🔒 Security Review	✅ Completed 2026-10-15T16:09:26.988440Z	cbbd732	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

Both debugger metric types receive the shared debugger namespace, and the telemetry pipeline forwards it without restrictions. Release compatibility depends on the intake support described in the PR being deployed.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Bits Code Review · Commit cbbd732}

[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.02 s	13.93 s	[-0.1%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.88 s	12.94 s	[-1.1%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	17.11 s	17.08 s	[-0.7%; +1.1%] (no difference)
startup:petclinic:iast:Agent	16.97 s	17.09 s	[-1.4%; +0.1%] (no difference)
startup:petclinic:profiling:Agent	16.74 s	16.42 s	[-2.5%; +6.4%] (no difference)
startup:petclinic:sca:Agent	17.02 s	17.03 s	[-1.0%; +0.9%] (no difference)
startup:petclinic:tracing:Agent	16.24 s	16.08 s	[-0.2%; +2.2%] (no difference)

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

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-10-15 16:53:32 UTC ℹ️ Start processing command /merge

---

2026-10-15 16:53:36 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-10-15 17:11:05 UTC ⚠️ MergeQueue: This merge request build was cancelled

thomas.watson@datadoghq.com cancelled this merge request build