datadog-agent
datadog-agent copied to clipboard
[Backport 7.52.x] [CWS] Do not include built-in variables in event context
Backport cebbda1600366702c249358d24b480ba71c917a8 from #23143.
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: 35882b2d-3797-458f-9d75-c43056352689 Baseline: 9bb4311242520cf27b1c4faeb3bab3f4d91113a5 Comparison: 846d8b3d598fc02e83ca86b8a00ecd7537aa9393 Total CPUs: 7
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
Experiments with missing or malformed data
- basic_py_check
Usually, this warning means that there is no usable optimization goal data for that experiment, which could be a result of misconfiguration.
No significant changes in experiment optimization goals
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Experiments ignored for regressions
Regressions in experiments with settings containing erratic: true are ignored.
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +0.20 | [-6.36, +6.76] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.04 | [-0.39, +2.47] |
| ➖ | file_tree | memory utilization | +0.63 | [+0.54, +0.71] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.62 | [+0.59, +0.65] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.56 | [+0.53, +0.60] |
| ➖ | otel_to_otel_logs | ingress throughput | +0.56 | [-0.07, +1.19] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.40 | [+0.34, +0.45] |
| ➖ | idle | memory utilization | +0.25 | [+0.22, +0.28] |
| ➖ | file_to_blackhole | % cpu utilization | +0.20 | [-6.36, +6.76] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | trace_agent_json | ingress throughput | -0.00 | [-0.01, +0.00] |
| ➖ | process_agent_standard_check | memory utilization | -0.07 | [-0.11, -0.04] |
Explanation
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".