-
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
[system-probe] Add packet counting to existing UDP byte counters #28546
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=42853416 --os-family=ubuntu Note: This applies to commit b9a0ad6 |
eBPF complexity changesSummary result: ✅ - stable
tracer detailstracer
This report was generated based on the complexity data for the current branch HEAD (pipeline [https://gitlab.ddbuild.io/DataDog/datadog-agent/-/pipelines/42483018]42483018) and the main branch (commit fe13dea). Objects without changes are not reported. Contact #ebpf-platform if you have any questions/feedback. Table complexity legend: 🔵 - new; ⚪ - unchanged; 🟢 - reduced; 🔴 - increased |
can you add a description? also it's helpful to put the ticket # in the title and/or under the |
Regression DetectorRegression Detector ResultsRun ID: f71704c0-7619-46c5-8e50-c37c9f99ecf3 Metrics dashboard Target profiles Baseline: 207b216 Performance changes are noted in the perf column of each table:
No significant changes in experiment optimization goalsConfidence level: 90.00% There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
|
perf | experiment | goal | Δ mean % | Δ mean % CI | links |
---|---|---|---|---|---|
➖ | basic_py_check | % cpu utilization | +0.96 | [-1.59, +3.51] | Logs |
➖ | otel_to_otel_logs | ingress throughput | +0.28 | [-0.53, +1.09] | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.00, +0.00] | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | Logs |
➖ | file_tree | memory utilization | -0.21 | [-0.27, -0.15] | Logs |
➖ | idle | memory utilization | -0.53 | [-0.57, -0.50] | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.73 | [-1.51, +0.05] | Logs |
➖ | pycheck_lots_of_tags | % cpu utilization | -0.82 | [-3.18, +1.54] | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | -4.32 | [-16.70, +8.06] | Logs |
Bounds Checks
perf | experiment | bounds_check_name | replicates_passed |
---|---|---|---|
✅ | idle | memory_usage | 10/10 |
Explanation
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".
9ba64e0
to
ebe8f63
Compare
going to test ipv6 instead if it's not already
9b93718
to
036bfaa
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.
Docs 👍
/merge |
🚂 MergeQueue: pull request added to the queue The median merge time in Use |
What does this PR do?
This PR begins tracing UDP packet counts in the agent and adds some tests to ensure it works as expected for both IPv4 and IPv6.
Motivation
Context - NPM-2973. The agent already has tracked UDP byte counts so it was determined we can leverage the existing kprobes to track packet counts in the same places.
Additional Notes
Possible Drawbacks / Trade-offs
This does not track UDP sends that have corking or MSG_MORE which are not commonly used. Doing this requires tracing
udp_send_skb
which probably will have to wait until after we deprecate prebuilt as mentioned in this threadDescribe how to test/QA your changes
This PR leverages the existing test suite and adds some new ones: