-
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
add common generic Get for system-probe checks #31254
Conversation
Go Package Import DifferencesBaseline: 4b26774
|
Test changes on VMUse this command from test-infra-definitions to manually test this PR changes on a VM: inv create-vm --pipeline-id=49668349 --os-family=ubuntu Note: This applies to commit 4ebf049 |
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 4b26774 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | file_tree | memory utilization | +0.77 | [+0.64, +0.90] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.61 | [+0.56, +0.66] | 1 | Logs bounds checks dashboard |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.52 | [-0.21, +1.26] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | +0.52 | [+0.40, +0.63] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.28 | [+0.21, +0.36] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.24 | [-0.23, +0.70] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.03 | [-0.72, +0.79] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.01] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.10, +0.09] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.03 | [-0.74, +0.68] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.04 | [-0.82, +0.74] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.05 | [-0.91, +0.80] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.11 | [-0.74, +0.52] | 1 | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -0.64 | [-4.08, +2.80] | 1 | Logs |
➖ | otel_to_otel_logs | ingress throughput | -0.68 | [-1.33, -0.02] | 1 | Logs |
➖ | basic_py_check | % cpu utilization | -1.75 | [-5.53, +2.02] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | file_to_blackhole_1000ms_latency | lost_bytes | 0/10 | |
✅ | 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 |
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.
} | ||
|
||
func constructURL(module string, endpoint string) string { | ||
u, _ := url.Parse("http://sysprobe") |
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.
since the operation is constant and it won't change if module
and endpoint
will be different, there is no need to preform the redundant parsing, and instead let's create a simple object that contains whatever you need
return data, err | ||
} | ||
|
||
func constructURL(module string, endpoint string) string { |
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.
why do we need that function?
isn't url.JoinPath("http://sysprobe", module, endpoint)
sufficient?
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.
url.JoinPath
doesn't support query parameters, while this function does. It isn't important for the generic checks, but there are other endpoints which use query parameters. Thus this property becomes important for some of the follow up PRs.
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.
it does support query params
https://go.dev/play/p/fKevIj3hvh6
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'm not sure we actually need unescape, I'm assuming http client knows how to handle it
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.
👍🏻 LGTM for files owned by @DataDog/container-integrations.
8878e6f
to
7a3925c
Compare
e5464c0
to
00b2bf2
Compare
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.
approved for wkit file
00b2bf2
to
4ebf049
Compare
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.
actually approved for 1 wkit file
/merge |
Devflow running:
|
What does this PR do?
Adds a
GetCheck
function to the system-probe client that handles the common use case for checks, which is requesting and unmarshaling JSON data.Motivation
Split PR from #30936
Describe how to test/QA your changes
Tested manually and on staging.
Possible Drawbacks / Trade-offs
Additional Notes
Stacked PR on top of #31211