[watson]

Summary

The debugger team agreed that every tracer reports its debugger metrics in a shared debugger instrumentation telemetry namespace, instead of live_debugger or dynamic_instrumentation (DEBUG-6335). This adds a cross-tracer test for it in the DEBUGGER_TELEMETRY scenario.

Test_Debugger_Telemetry_Metrics::test_events_skipped_rate_limit_probe
  setup
    install a snapshot line probe (probe_snapshot_log_line, /debugger/log)
    hit it 50 times in a row          # 1 snapshot/s, but Java/.NET can burst up to 17
    wait up to 60s for the telemetry flush
  test
    no metric series in live_debugger / dynamic_instrumentation
    events.skipped tagged reason:rateLimitProbe in debugger
      type == count, sum(points) > 0

The test only relies on reason:rateLimitProbe, the one guardrail every tracer already emits. Java doesn't send event_type.

Manifests enable it where the change has shipped or reached dev builds, using the weblogs where the line-probe snapshot tests run:

Tracer	Change	Manifest
Ruby	DataDog/dd-trace-rb#6484, released in 2.46.0	enabled from v2.46.0 (rails72, rails80, uds-rails)
Java	DataDog/dd-trace-java#12892, merged	enabled from v1.68.0-SNAPSHOT (Spring Boot weblogs)
Node.js	DataDog/dd-trace-js#10757, on the v6.22.0 / v5.133.0 release proposals	enabled from >=6.22.0 || ^5.133.0 (all weblogs but nextjs)
.NET	DataDog/dd-trace-dotnet#9423, merged, ships in 3.57.0	enabled from v3.57.0-dev (all weblogs)
Python	DataDog/dd-trace-py#21041 (draft), and its guardrail metric names don't match events.skipped yet	missing_feature
Go, PHP	no debugger telemetry metrics yet	missing_feature

The intake allows the namespace in ddoghq/dd-go#23524.

Evidence

• The test's parsing helpers were checked offline against synthetic generate-metrics and sketches payloads, covering payload-level and per-series namespaces.
• ./format.sh passes.
• I couldn't run the scenario end to end locally: the Node.js weblog base image is amd64-only and the weblog didn't start under emulation on my arm64 host.

Merge Danger

Door: two-way

Blast Radius: small

The new test runs for Ruby, Java, Node.js and .NET. It has never run end to end before (see Evidence), so their CI jobs are its first real run.

🤖 Generated with Claude Code

[github-actions]

CODEOWNERS have been resolved as:

manifests/dotnet.yml                                                    @DataDog/system-tests-reviewers
manifests/golang.yml                                                    @DataDog/system-tests-reviewers
manifests/java.yml                                                      @DataDog/system-tests-reviewers
manifests/nodejs.yml                                                    @DataDog/system-tests-reviewers
manifests/php.yml                                                       @DataDog/system-tests-reviewers
manifests/python.yml                                                    @DataDog/system-tests-reviewers
manifests/ruby.yml                                                      @DataDog/system-tests-reviewers
tests/debugger/test_debugger_telemetry.py                               @DataDog/debugger

[datadog-official]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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