-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Add ^ and $ to 'excluded_filesystems' and 'excluded_disks' config keys #37752
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: fb0309c Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +2.14 | [-0.68, +4.96] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle | memory utilization | +0.79 | [+0.73, +0.86] | 1 | Logs bounds checks dashboard |
➖ | quality_gate_idle_all_features | memory utilization | +0.12 | [+0.04, +0.20] | 1 | Logs bounds checks dashboard |
➖ | otlp_ingest_logs | memory utilization | +0.10 | [-0.03, +0.23] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.09 | [-0.45, +0.63] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.07 | [-0.49, +0.64] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.06 | [-0.55, +0.66] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.04 | [-0.54, +0.63] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.03 | [-0.58, +0.64] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.55, +0.58] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.27, +0.26] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.05 | [-0.29, +0.19] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.06 | [-0.18, +0.06] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.08 | [-0.23, +0.06] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.10 | [-0.26, +0.07] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.14 | [-0.76, +0.49] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.22 | [-0.27, -0.16] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.30 | [-0.35, -0.25] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.64 | [-0.74, -0.55] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.83 | [-1.71, +0.05] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | -1.41 | [-4.36, +1.54] | 1 | Logs |
➖ | file_tree | memory utilization | -2.61 | [-2.81, -2.42] | 1 | Logs |
Bounds Checks: ✅ Passed
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_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_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_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.
- quality_gate_idle_all_features, 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.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
regExpList := []regexp.Regexp{} | ||
for _, slice := range slices { | ||
for _, val := range slice { | ||
expr := fmt.Sprintf("^%s$", val) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://github.com/DataDog/integrations-core/blob/master/disk/datadog_checks/disk/disk.py#L365
it does not look like the python version adds the beginning anchor (^
)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right. But not needed because it's implicit.
We use Pattern.match here and according to its documentation:
If zero or more characters at the beginning of string match this regular expression, return a corresponding Match. Return None if the string does not match the pattern; note that this is different from a zero-length match.
However, in the go
version we need to explicitly indicate this to reproduce the same behavior as in python
since MatchString used here behaves differently, returning true
if it finds the string, regardless of the position.
MatchString reports whether the string s contains any match of the regular expression re.
Added some tests to confirm this point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've updated the PR description to make this clearer.
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
This PR updates the regular expression handling in Go to ensure consistent behavior with the previous Python implementation for 'excluded_filesystems' and 'excluded_disks' config keys.
Motivation
In the original Python code, exclude patterns were applied using re.match(), which implicitly anchors the pattern at the start of the string. Additionally, we were appending a $ to the pattern, effectively enforcing that the entire string must match the given word (i.e., full-string match).
In Go, regexp.MatchString() behaves different, it matches anywhere in the string unless explicitly anchored. As a result, patterns like
tmpfs$
were incorrectly matching strings likedevtmpfs
as we detected during our deployment on staging.To ensure equivalent semantics, we now explicitly wrap all exclude patterns with
^
and$
, so that MatchString() behaves like a full-string match (^pattern$). This guarantees that only exact matches (as originally intended) are excluded.Describe how you validated your changes
Following a TDD methodology when fixing a bug, the first thing added were tests that failed, and then the code that fixed them was added.
Possible Drawbacks / Trade-offs
Additional Notes