datadog-agent
datadog-agent copied to clipboard
[Backport 7.52.x] Restrict value_name to SetRegistryKeyValueEvent
Backport eca5bc2d3b6a16817f28a3b34ba620d00f20431d from #23259.
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: 43d7af18-1b27-4137-bf49-9a5a7ef1a960 Baseline: dd072e89e16675fdef57f1044a618e0303ede6a9 Comparison: 32c7f881e0ad8c58def43f226c896efea597d47e 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 | +1.04 | [-5.55, +7.62] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | +1.04 | [-5.55, +7.62] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.64 | [+0.60, +0.69] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.33 | [+0.27, +0.38] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.17 | [+0.12, +0.22] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.02 | [+0.01, +0.03] |
| ➖ | 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.01 | [-0.03, +0.01] |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.15 | [-1.56, +1.26] |
| ➖ | idle | memory utilization | -0.30 | [-0.33, -0.27] |
| ➖ | otel_to_otel_logs | ingress throughput | -0.35 | [-0.98, +0.29] |
| ➖ | process_agent_standard_check | memory utilization | -0.57 | [-0.61, -0.53] |
| ➖ | file_tree | memory utilization | -0.91 | [-1.03, -0.79] |
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".
/merge
:steam_locomotive: MergeQueue
Pull request added to the queue.
This build is going to start soon! (estimated merge in less than 53m)
Use /merge -c to cancel this operation!