-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Set 'HostProcMountinfo' for Disk integration #37826
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
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 39ac529 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_cpu | % cpu utilization | +2.35 | [-0.72, +5.42] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +1.99 | [+1.13, +2.85] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.72 | [+0.63, +0.81] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle | memory utilization | +0.31 | [+0.25, +0.37] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.25 | [+0.20, +0.30] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.24 | [+0.12, +0.36] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.15 | [+0.01, +0.29] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.07 | [-0.48, +0.61] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.02 | [-0.60, +0.63] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.01 | [-0.54, +0.56] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.00 | [-0.24, +0.24] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.29, +0.28] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.03 | [-0.55, +0.49] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.03 | [-0.60, +0.54] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.07 | [-0.67, +0.53] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.07 | [-0.66, +0.51] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.20 | [-0.36, -0.04] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.21 | [-0.33, -0.08] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.32 | [-0.38, -0.25] | 1 | Logs |
➖ | file_tree | memory utilization | -0.50 | [-0.66, -0.34] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -1.12 | [-1.19, -1.04] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -4.43 | [-7.12, -1.74] | 1 | Logs bounds checks dashboard |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | file_to_blackhole_0ms_latency_http2 | lost_bytes | 9/10 | |
✅ | 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_0ms_latency_http1 | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency_http1 | memory_usage | 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_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 | 10/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 |
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
✅ Passed. All Quality Gates 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_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
/merge |
View all feedbacks in Devflow UI.
This merge request is not mergeable yet, because of pending checks/missing approvals. It will be added to the queue as soon as checks pass and/or get approvals.
The expected merge time in
|
What does this PR do?
This PR introduces a new configuration option
proc_mountinfo_path
(defaulting to "/proc/self/mounts
") and updates our disk check to calldisk.PartitionsWithContext(ctx, includeAll)
instead of the previous call todisk.Partitions(includeAll)
fromgopsutil
Motivation
When migrating our disk checks from Python’s
psutil
to Go’sgopsutil
, we discovered that by default:psutil
reads mount information from the current process’s namespace (/proc/self/mounts
).gopsutil
reads from/proc/1/mountinfo
, which doesn’t reflect the container’s view.These differences led to inconsistent results inside containers (see here). This PR introduces a new
proc_mountinfo_path
config (defaulting to "/proc/self/mounts
") and switches all disk-check calls toPartitionsWithContext
(instead ofPartitions
). By carrying the override in the context, we now have per-call control of the mountinfo source, makinggopsutil
behave likepsutil
by default, while still retaining its full fallback logic for other advanced scenarios.Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes