Exclude OTLP header and Datadog key configs from telemetry

[bm1549]

Description

Stops configuration telemetry from reporting DD_API_KEY or OTLP exporter header values.

DD_API_KEY now uses a sensitivity flag carried through ZAI config metadata. The OTLP header configs remain in supported-config metadata with sensitive: true, but are rejected at the PHP whitelist and native ingestion boundaries. DD_TRACE_ENABLED remains omitted separately because its shutdown-time value is not meaningful.

The metadata generator now reads sensitivity from all config headers and uses comment/string-aware parsing. Its CI self-test covers parser edge cases. Runtime coverage checks the native bypass path and a future OTLP traces header variant, with safe configs as positive controls.

Reviewer checklist

• Test coverage seems ok.
• Appropriate labels assigned.

[datadog-datadog-prod-us1-2]

 

✨ Unblock PR with BitsAI

⚠️ Warnings

❌ Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 7 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-php | Loader test on arm64 libc: [8.4, zts, arm64] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-php | merge-gate — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

DataDog/apm-reliability/dd-trace-php | test_extension_ci: [7.4] — 🔧 Needs a code fix, caused by this PR

View more details · View in GitLab

View all 7 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 60.65% (-0.01%)

Useful? React with 👍 / 👎

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

[pr-commenter]

Benchmarks [ tracer ]

Benchmark execution time: 2026-09-02 16:12:53

Comparing candidate commit 1314586 in PR branch brian.marks/omit-sensitive-config-telemetry with baseline commit 2ad9386 in branch master.

Found 4 performance improvements and 3 performance regressions! Performance is the same for 185 metrics, 2 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:HookBench/benchHookOverheadTraceFunction-opcache

• 🟩 execution_time [-10.162µs; -3.919µs] or [-5.892%; -2.272%]

scenario:MessagePackSerializationBench/benchMessagePackSerialization-opcache

• 🟩 execution_time [-3.522µs; -2.458µs] or [-3.057%; -2.134%]

scenario:SamplingRuleMatchingBench/benchRegexMatching2

• 🟥 execution_time [+91.459ns; +150.941ns] or [+6.277%; +10.360%]

scenario:SamplingRuleMatchingBench/benchRegexMatching3

• 🟥 execution_time [+30.964ns; +108.836ns] or [+2.066%; +7.263%]

scenario:SamplingRuleMatchingBench/benchRegexMatching4

• 🟥 execution_time [+43.977ns; +91.023ns] or [+2.977%; +6.161%]

scenario:SpanBench/benchOpenTelemetryInteroperability

• 🟩 execution_time [-222.527µs; -218.960µs] or [-52.769%; -51.923%]

scenario:TraceAnnotationsBench/benchTraceAnnotationOverhead-opcache

• 🟩 execution_time [-9.750µs; -4.692µs] or [-5.393%; -2.596%]

[pr-commenter]

Benchmarks [ profiler ]

Benchmark execution time: 2026-09-02 15:23:55

Comparing candidate commit 1314586 in PR branch brian.marks/omit-sensitive-config-telemetry with baseline commit 2ad9386 in branch master.

Found 1 performance improvements and 0 performance regressions! Performance is the same for 25 metrics, 10 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

• 🟩 = significantly better candidate vs. baseline
• 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:php-profiler-timeline-memory-with-profiler

• 🟩 cpu_system_time [-44.433ms; -15.741ms] or [-6.730%; -2.384%]

[bwoebi]

I've rewrote the code to be much simpler, I think we can now merge that.