datadog-agent
datadog-agent copied to clipboard
Bump github.com/aws/aws-sdk-go-v2/service/ec2 from 1.138.1 to 1.149.1 in /test/new-e2e
Bumps github.com/aws/aws-sdk-go-v2/service/ec2 from 1.138.1 to 1.149.1.
Commits
7095341Release 2024-02-23bcf04e6Regenerated Clientsca190b0Update API model6397a64move common middleware stack ops to service client modules (#2516)e9b00e2Release 2024-02-220cfc53eRegenerated Clients92d6c19Update API model18adb31add middleware snapshot tests (#2513)7888f0eRelease 2024-02-214a9cd1dRegenerated Clients- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Bloop Bleep... Dogbot Here
Regression Detector Results
Run ID: 8146b781-08e2-4575-9cf3-bd66bbeaabaa Baseline: 57c16d2ff86cf11c0abfed5c4f929dd1cbc492b3 Comparison: f543fe79e7e97cbdb6d7d6056f9ff4cb0821ed58 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.37 | [-6.90, +6.15] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +3.50 | [+2.07, +4.94] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.56 | [+0.50, +0.62] |
| ➖ | otel_to_otel_logs | ingress throughput | +0.38 | [-0.25, +1.02] |
| ➖ | process_agent_standard_check | memory utilization | +0.15 | [+0.11, +0.19] |
| ➖ | process_agent_real_time_mode | memory utilization | +0.15 | [+0.11, +0.19] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.00 | [-0.00, +0.01] |
| ➖ | 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.04 | [-0.07, -0.01] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | -0.29 | [-0.33, -0.26] |
| ➖ | idle | memory utilization | -0.35 | [-0.39, -0.30] |
| ➖ | file_to_blackhole | % cpu utilization | -0.37 | [-6.90, +6.15] |
| ➖ | file_tree | memory utilization | -0.41 | [-0.50, -0.33] |
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".
Superseded by #23404.