Add Battery Check for Windows#43789
Conversation
Go Package Import DifferencesBaseline: 791d697
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 791d697 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.09 | [-1.97, +4.16] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.09 | [-1.97, +4.16] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.93 | [+0.77, +1.09] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +0.51 | [-0.96, +1.99] | 1 | Logs bounds checks dashboard |
| ➖ | docker_containers_memory | memory utilization | +0.33 | [+0.25, +0.41] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.10 | [-0.11, +0.31] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.08 | [+0.03, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.06 | [-0.34, +0.45] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.01 | [-0.40, +0.42] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.01 | [-0.13, +0.14] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.00 | [-0.04, +0.05] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.07, +0.07] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.13, +0.13] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.01 | [-0.06, +0.03] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.05 | [-0.26, +0.15] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.45, +0.29] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.09 | [-0.15, -0.03] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | -0.16 | [-0.31, -0.02] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.27 | [-0.34, -0.20] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.27 | [-0.33, -0.22] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.50 | [-0.60, -0.40] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.52 | [-0.74, -0.30] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.63 | [-0.86, -0.40] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.83 | [-0.89, -0.77] | 1 | Logs |
Bounds Checks: ❌ Failed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | docker_containers_cpu | simple_check_run | 10/10 | |
| ✅ | docker_containers_memory | memory_usage | 10/10 | |
| ✅ | docker_containers_memory | simple_check_run | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_0ms_latency | memory_usage | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | 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_500ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_500ms_latency | memory_usage | 10/10 | |
| ✅ | quality_gate_idle | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_idle_all_features | intake_connections | 10/10 | bounds checks dashboard |
| ❌ | quality_gate_idle_all_features | memory_usage | 9/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_logs | memory_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | memory_usage | 10/10 | bounds checks dashboard |
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_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
nathan-b
left a comment
There was a problem hiding this comment.
A few comments; I don't know if any of them are blockers but PTAL to make sure :)
nathan-b
left a comment
There was a problem hiding this comment.
Thanks for working through the comments!
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
### What does this PR do? This PR is a continuation of #43789 but this time to collect battery metrics on MacOS devices. ### Motivation https://datadoghq.atlassian.net/browse/WINA-2068 ### Describe how you validated your changes - Standalone project on work mac laptop + unit tests - Built the agent ``` dda inv agent.build --build-exclude=systemd cp /Users/brian.tu/go/src/github.com/DataDog/datadog-agent/bin/agent/dist/conf.d/battery.d/conf.yaml.example /Users/brian.tu/go/src/github.com/DataDog/datadog-agent/bin/agent/dist/conf.d/battery.d/conf.yaml ./bin/agent/agent check battery ``` ### Additional Notes Co-authored-by: mrafi97 <[email protected]> Co-authored-by: brian.tu <[email protected]>
What does this PR do?
This PR adds the battery check implementation for Windows. The battery check will collect metrics for the system battery in a Windows host. The check will not run if there is no battery detected in the system.
Motivation
https://datadoghq.atlassian.net/browse/WINA-2033
Describe how you validated your changes
Enable the battery check by setting the following in
battery.d/conf.yaml:Restart the Agent and run a check run command to ensure that metrics are collected:
Additional Notes