datadog-agent
datadog-agent copied to clipboard
[Backport 7.52.x] [EBPF-377]: [Rollback] changed back the ebpf telemetry metrics from Counter to Gauge.
Backport be0856cfe29e5b8f49d14b49941921b16b84be2a from #23191.
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: 7c05b304-0116-4c7d-8078-b94a00a17ed1 Baseline: 6e268a33a252115c8fb5e0b6d93ff0e0188a45a8 Comparison: c82072640b4765f8b15f1f145da6798dd72ab5e0 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.80 | [-7.32, +5.73] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.29 | [-0.16, +2.74] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.34 | [+0.30, +0.38] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.28 | [+0.21, +0.34] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.01 | [-0.00, +0.03] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | trace_agent_json | ingress throughput | -0.00 | [-0.03, +0.03] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | -0.10 | [-0.13, -0.07] |
| ➖ | idle | memory utilization | -0.11 | [-0.14, -0.07] |
| ➖ | otel_to_otel_logs | ingress throughput | -0.19 | [-0.83, +0.45] |
| ➖ | file_tree | memory utilization | -0.34 | [-0.42, -0.26] |
| ➖ | process_agent_standard_check | memory utilization | -0.64 | [-0.68, -0.60] |
| ➖ | file_to_blackhole | % cpu utilization | -0.80 | [-7.32, +5.73] |
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".
I am closing this auto-generated PR, since i did it manualy