-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[CNM-4440] Add TCP SYN traceroute driver #37433
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
base: main
Are you sure you want to change the base?
Conversation
Uncompressed package size comparisonComparison with ancestor Diff per package
Decision✅ Passed |
2d8fcc7
to
d410d19
Compare
ecf7a0c
to
b460cd5
Compare
53c0e92
to
ed0ec1c
Compare
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: c24df94 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +0.98 | [+0.05, +1.91] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.43 | [+0.38, +0.48] | 1 | Logs |
➖ | ddot_metrics | memory utilization | +0.40 | [+0.28, +0.51] | 1 | Logs |
➖ | docker_containers_cpu | % cpu utilization | +0.31 | [-2.64, +3.25] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.09 | [-0.15, +0.32] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.08 | [-0.53, +0.69] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.04 | [-0.54, +0.63] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.01 | [-0.63, +0.64] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.01 | [-0.26, +0.28] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.01, +0.02] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.00 | [-0.61, +0.60] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.02 | [-0.61, +0.56] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | -0.02 | [-0.18, +0.13] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.03 | [-0.10, +0.04] | 1 | Logs bounds checks dashboard |
➖ | tcp_syslog_to_blackhole | ingress throughput | -0.04 | [-0.11, +0.02] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.05 | [-0.67, +0.57] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | -0.07 | [-0.68, +0.53] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.21 | [-0.35, -0.08] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.22 | [-0.29, -0.14] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -0.24 | [-0.38, -0.10] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.25 | [-0.38, -0.13] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | -1.39 | [-1.57, -1.22] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -2.84 | [-5.55, -0.12] | 1 | Logs bounds checks dashboard |
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_logs, 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 intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, 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.
One comment about file naming: e.g., for the files under tcp
folder, the prefix tcp_
seems redundant. Same for the files under the packets
folder.
Stacked on [NPM-4440] Move packet capture to separate package, add Sink interface
What does this PR do?
tcpDriver
, an implementation ofTracerouteDriver
for TCP SYN.Source
andSink
, the platform-agnostic packet interfacestcpDriver
uses.tcpDriver
which uses the mockscommon
package to support thisportable_syn
which runs a traceroute withtcpDriver
.Motivation
Working towards replacing the traceroute implementations with platform-agnostic and (mostly) IPv4/IPv6 agnostic versions.
Remaining work:
TracerouteDriver
RawConn
implementSource
andSink
so all our traceroutes work on Windows tooDescribe how you validated your changes
I added a big test suite for
tcpDriver
intcp_driver_test.go
which you can run via:Possible Drawbacks / Trade-offs
Tests don't cover paris traceroute mode right now, but hopefully we are removing that mode.
Additional Notes