-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[AGENTRUN-310] Fix FIPS Agent status output #37594
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: f07a0ac Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_cpu | % cpu utilization | +1.22 | [-1.90, +4.33] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.49 | [+0.45, +0.53] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.48 | [+0.37, +0.59] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.47 | [+0.39, +0.55] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.45 | [-0.43, +1.34] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.43 | [+0.26, +0.60] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.28 | [+0.23, +0.34] | 1 | Logs bounds checks dashboard |
➖ | ddot_logs | memory utilization | +0.16 | [+0.02, +0.30] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.10 | [-0.02, +0.23] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.08 | [-0.15, +0.32] | 1 | Logs |
➖ | file_tree | memory utilization | +0.03 | [-0.10, +0.17] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.03 | [-0.63, +0.70] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.01 | [-0.65, +0.67] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.01 | [-0.62, +0.63] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.00 | [-2.75, +2.76] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.27, +0.28] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.04 | [-0.62, +0.54] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.04 | [-0.67, +0.59] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.06 | [-0.66, +0.55] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.09 | [-0.74, +0.55] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.38 | [-0.43, -0.32] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -0.40 | [-0.45, -0.34] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | docker_containers_memory | memory_usage | 0/10 | |
✅ | docker_containers_cpu | simple_check_run | 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_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.
- quality_gate_logs, 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_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
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.
Left some minor feedback for style and consistency with other release notes
--- | ||
fixes: | ||
- | | ||
Removed the FIPS Proxy status section from the agent status page when running the FIPS Agent. |
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.
Removed the FIPS Proxy status section from the agent status page when running the FIPS Agent. | |
Remove the FIPS Proxy status section from the Agent status page when running the FIPS Agent. |
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.
@buraizu QQ: Since these are put into the release notes, would it make more sense for them to be past-tense?
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.
@sgnn7 good question, thanks for following up. Release notes are generally kept in present tense to clearly indicate that the change is available in the current version. This is the pattern followed by most of our other release notes as well.
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.
May be good to communicate this wider in the Agent group as we're a bit inconsistent on this https://github.com/DataDog/datadog-agent/releases 😅
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
(cherry picked from commit 0b19806)
(cherry picked from commit 0b19806)
What does this PR do?
This PR prevent from printing the FIPS Proxy status section when the
status
command is executed with the FIPS Agent.The FIPS Proxy status should be printed only when:
fips.enabled
config is set to trueMotivation
This PR fix a regression introduced in #36988
Describe how you validated your changes
Possible Drawbacks / Trade-offs
Additional Notes