[serverless-init] Skip trace/metric init when DD_API_KEY is not set#48458
Conversation
When serverless-init runs without DD_API_KEY configured, the trace agent config validation and forwarder produce repeated ERROR logs (403 responses, missing API key errors). This regressed in 1.9.0 when the internal log level was changed from "off" to "error". Gate trace and metric agent initialization on API key presence. When no key is set, log a single warning and use no-op agents. The process wrapper and logs agent continue to function normally. Fixes #48036 Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
All contributors have signed the CLA ✍️ ✅ |
Files inventory check summaryFile checks results against ancestor 867176f1: Results for datadog-agent_7.79.0~devel.git.219.7daeadc.pipeline.105105202-1_amd64.deb:No change detected |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 6e6fb95 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.32 | [-1.65, +4.29] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.32 | [-1.65, +4.29] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +1.07 | [+1.00, +1.14] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | +0.80 | [+0.70, +0.90] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.28 | [+0.11, +0.45] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.23 | [+0.17, +0.29] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | +0.19 | [+0.11, +0.26] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.17 | [-0.06, +0.41] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.17 | [+0.01, +0.34] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +0.12 | [-0.05, +0.28] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | +0.09 | [+0.06, +0.13] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.03 | [-0.51, +0.58] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.03 | [-0.39, +0.45] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.07, +0.09] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.01 | [-0.10, +0.12] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.20, +0.19] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.02 | [-0.41, +0.36] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | -0.03 | [-0.24, +0.17] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -0.05 | [-1.67, +1.57] | 1 | Logs bounds checks dashboard |
| ➖ | file_tree | memory utilization | -0.06 | [-0.12, +0.00] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | -0.20 | [-0.25, -0.15] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.36 | [-0.58, -0.14] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.54 | [-0.73, -0.34] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.64 | [-0.78, -0.50] | 1 | Logs |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | observed_value | links |
|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | 601 ≥ 26 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | 273.10MiB ≤ 370MiB | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | 703 ≥ 26 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | 0.19GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_0ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | 0.23GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_1000ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | 0.20GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_100ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | 0.22GiB ≤ 1.20GiB | |
| ✅ | file_to_blackhole_500ms_latency | missed_bytes | 10/10 | 0B = 0B | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | 3 = 3 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | 173.66MiB ≤ 175MiB | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | 3 = 3 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | memory_usage | 10/10 | 491.12MiB ≤ 550MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | 4 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | 203.08MiB ≤ 220MiB | bounds checks dashboard |
| ✅ | quality_gate_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | 366.20 ≤ 2000 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | 3 ≤ 6 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | 405.84MiB ≤ 475MiB | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | missed_bytes | 10/10 | 0B = 0B | bounds checks dashboard |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
Performance changes are noted in the perf column of each table:
- ✅ = significantly better comparison variant performance
- ❌ = significantly worse comparison variant performance
- ➖ = no significant change in performance
A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".
For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:
-
Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.
-
Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.
-
Its configuration does not mark it "erratic".
CI Pass/Fail Decision
✅ Passed. All Quality Gates passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check missed_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates 30 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
77db2e5 to
c923fee
Compare
Replace nested monitoringEnabled conditionals with a guard clause that returns early when DD_API_KEY is unset. Also use configUtils.SanitizeAPIKey instead of inline strings.TrimSpace, and remove the now-unreachable ErrMissingAPIKey branch in trace agent config loading. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
c923fee to
ff53180
Compare
…e field Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
I have read the CLA Document and I hereby sign the CLA |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ff05077d08
ℹ️ About Codex in GitHub
Codex has been enabled to automatically 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
…guard The early return that disables trace/metric init when no API key is set now also checks the deprecated apm_config.api_key, which the trace agent still honors. This prevents a silent regression for any deployments that only set that key. Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
|
23f7c50
into
main
Summary
DD_API_KEY, the trace agent config validation and forwarder produced repeated ERROR logs (403 responses, missing API key). This regressed in 1.9.0 when the internal log level changed from"off"to"error".ErrMissingAPIKeyfrom Error to Warn in trace agent config loading.Fixes #48036
Test plan
docker runwith serverless-init dev image withoutDD_API_KEY— expect single WARN, no ERROR spamdocker runwith serverless-init withDD_API_KEY— expect normal trace/metric behavior🤖 Generated with Claude Code