-
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
usm: config: Default USM configuration should not warn about using network_config.enable_https_monitoring #31639
Conversation
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=50217550 --os-family=ubuntu Note: This applies to commit 582afdf |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 0200b9d Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | quality_gate_logs | % cpu utilization | +1.77 | [-1.26, +4.79] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.80 | [+0.06, +1.55] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.81, +0.83] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.11, +0.11] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.01 | [-0.66, +0.63] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.08 | [-0.85, +0.70] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.15 | [-0.79, +0.48] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | -0.15 | [-0.63, +0.32] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.22 | [-0.98, +0.55] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.30 | [-0.35, -0.25] | 1 | Logs bounds checks dashboard |
➖ | otel_to_otel_logs | ingress throughput | -0.39 | [-1.05, +0.27] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.40 | [-0.45, -0.34] | 1 | Logs |
➖ | file_tree | memory utilization | -0.53 | [-0.68, -0.37] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -1.74 | [-1.88, -1.60] | 1 | Logs bounds checks dashboard |
➖ | pycheck_lots_of_tags | % cpu utilization | -2.37 | [-5.72, +0.99] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -3.34 | [-7.26, +0.58] | 1 | Logs |
Bounds Checks: ✅ Passed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
✅ | file_to_blackhole_0ms_latency | lost_bytes | 10/10 | |
✅ | file_to_blackhole_0ms_latency | 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 | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_idle_all_features | memory_usage | 10/10 | bounds checks dashboard |
✅ | quality_gate_logs | lost_bytes | 10/10 | |
✅ | quality_gate_logs | memory_usage | 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
✅ Passed. All Quality Gates passed.
- quality_gate_idle, 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_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
…twork_config.enable_https_monitoring Customers using the default configuration to enable USM will see a warning message indicating that a configuration key is deprecated. Enabling USM enables the old configuration for https monitoring, which later generates a warning, although the customer didn't explicitly use the deprecated configuration. The change enables by default the new configuration option, without changing the behavior for backward compatibility
cea38ab
to
37f0dc3
Compare
Blocked on #31567 |
/merge |
Devflow running:
|
What does this PR do?
This PR addresses a warning message generated when using the default configuration to enable USM.
The warning indicates that the configuration key
network_config.enable_https_monitoring
is deprecated and recommends usingservice_monitoring_config.tls.native.enabled
instead.The change ensures that the warning is not generated for the default configuration.
Motivation
Customers using the default configuration should not encounter warnings about deprecated configuration keys. This behavior may lead to confusion and unnecessary concerns, especially when no action is required for the default setup. The change improves the user experience and aligns with expected behavior.
Describe how to test/QA your changes
Covered by UTs
TestUSMTLSNativeEnabled
Manual QA:
Possible Drawbacks / Trade-offs
Additional Notes
The issue was identified due to the following code snippet generating a warning:
This ensures default settings align with the new configuration key without generating unnecessary warnings.