datadog-agent
datadog-agent copied to clipboard
[auto-team-labels] Set up auto team label assignation as github workflow
What does this PR do?
Adds a Github workflow to set automatically the team label if it can be deduced by changed files (using CODEOWNERS).
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
- Tested using a fork of this repo
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: 94a88493-f594-4736-9a96-5f5ce7ddb47d Baseline: 9ddb7c2e90fac70fcdabacc55aa1998a21c0cf1e Comparison: 96a5b58f9f7c0daddb3aac9ceae3756708333abb
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.55 | [-6.02, +7.12] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.01 | [-0.45, +2.47] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.67 | [+0.61, +0.73] |
| ➖ | file_to_blackhole | % cpu utilization | +0.55 | [-6.02, +7.12] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.12 | [+0.09, +0.16] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | +0.08 | [+0.04, +0.11] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.01 | [-0.01, +0.04] |
| ➖ | 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.03, +0.03] |
| ➖ | file_tree | memory utilization | -0.06 | [-0.12, -0.00] |
| ➖ | process_agent_standard_check | memory utilization | -0.12 | [-0.16, -0.08] |
| ➖ | idle | memory utilization | -0.40 | [-0.44, -0.37] |
| ➖ | otel_to_otel_logs | ingress throughput | -0.43 | [-1.06, +0.20] |
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 next! (estimated merge in less than 28m)
Use /merge -c to cancel this operation!