-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Checks agent process #31571
base: main
Are you sure you want to change the base?
Checks agent process #31571
Conversation
…/add-remote-autodiscovery
2c4f0d9
to
8e7fff7
Compare
…/add-remote-autodiscovery
…/add-remote-autodiscovery
…g/datadog-agent into checks-agent-process
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv aws.create-vm --pipeline-id=52535121 --os-family=ubuntu Note: This applies to commit cba7c51 |
This comment was marked as outdated.
This comment was marked as outdated.
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 49022d2 Optimization Goals: ❌ Regression(s) detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
❌ | quality_gate_idle | memory utilization | +15.89 | [+15.85, +15.93] | 1 | Logs bounds checks dashboard |
❌ | file_tree | memory utilization | +8.83 | [+8.70, +8.96] | 1 | Logs |
❌ | quality_gate_idle_all_features | memory utilization | +7.96 | [+7.87, +8.04] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.78 | [-0.01, +1.57] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.15 | [-0.50, +0.80] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.01 | [-0.83, +0.85] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.85, +0.86] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.11] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.69, +0.66] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.04 | [-0.51, +0.43] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.05 | [-1.00, +0.91] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.10 | [-0.87, +0.67] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -1.03 | [-4.22, +2.16] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -1.33 | [-1.40, -1.26] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.37 | [-2.05, -0.70] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_idle | memory_usage | 0/10 | bounds checks dashboard |
❌ | quality_gate_logs | memory_usage | 0/10 | |
❌ | quality_gate_idle_all_features | memory_usage | 2/10 | bounds checks dashboard |
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http2 | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_1000ms_latency_linear_load | memory_usage | 10/10 | |
✅ | file_to_blackhole_100ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_100ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_300ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_300ms_latency | memory_usage | 10/10 | |
✅ | file_to_blackhole_500ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
✅ | quality_gate_logs | lost_bytes | 10/10 |
Explanation
Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%
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
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".
CI Pass/Fail Decision
❌ Failed. Some Quality Gates were violated.
- quality_gate_idle, bounds check memory_usage: 0/10 replicas passed. Failed 10 which is > 0. Gate FAILED.
- quality_gate_idle_all_features, bounds check memory_usage: 2/10 replicas passed. Failed 8 which is > 0. Gate FAILED.
- quality_gate_logs, bounds check memory_usage: 0/10 replicas passed. Failed 10 which is > 0. Gate FAILED.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision |
e8ff4a4
to
9ea4dff
Compare
add more logging information
What does this PR do?
Motivation
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes