-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Extend setsockopt Tracking with Detailed Filter and Socket Data #38036
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
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: a9e95a7 Optimization Goals: ✅ No significant changes detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | docker_containers_cpu | % cpu utilization | +2.25 | [-0.91, +5.42] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | +0.68 | [+0.55, +0.81] | 1 | Logs |
➖ | docker_containers_memory | memory utilization | +0.44 | [+0.37, +0.52] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.37 | [+0.21, +0.54] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | +0.20 | [-2.59, +2.99] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_500ms_latency | egress throughput | +0.07 | [-0.49, +0.64] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | +0.06 | [-0.52, +0.64] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | +0.06 | [-0.01, +0.12] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.04 | [-0.56, +0.63] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | +0.03 | [-0.57, +0.64] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.03 | [-0.06, +0.12] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.03 | [-0.06, +0.12] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.02 | [-0.59, +0.63] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.01 | [-0.22, +0.25] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | +0.01 | [-0.59, +0.60] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.26, +0.27] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.00 | [-0.12, +0.12] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | -0.04 | [-0.64, +0.57] | 1 | Logs |
➖ | ddot_logs | memory utilization | -0.60 | [-0.70, -0.50] | 1 | Logs |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -1.48 | [-2.39, -0.57] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -2.38 | [-2.53, -2.23] | 1 | Logs bounds checks dashboard |
➖ | file_tree | memory utilization | -4.49 | [-4.70, -4.27] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | quality_gate_logs | memory_usage | 9/10 | bounds checks dashboard |
✅ | docker_containers_cpu | simple_check_run | 10/10 | |
✅ | docker_containers_memory | memory_usage | 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 |
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
❌ Failed. Some Quality Gates were violated.
- 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.
- quality_gate_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_logs, bounds check memory_usage: 9/10 replicas passed. Failed 1 which is > 0. Gate FAILED.
- quality_gate_logs, bounds check lost_bytes: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
if (syscall->setsockopt.filter_len > MAX_BPF_FILTER_LEN){ | ||
return 0; | ||
} | ||
send_event_with_size_ptr(ctx, EVENT_SETSOCKOPT, event, (offsetof(struct setsockopt_event_t, bpf_filters_buffer) + sizeof(struct sock_filter) * syscall->setsockopt.filter_len) ); | ||
|
||
// if the tail call fails, we need to pop the syscall cache entry | ||
pop_syscall(EVENT_SETSOCKOPT); |
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.
Unrelated to the changes of your PR but you don't need to pop the syscall here as you already do it at the beginning of the function
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.
You are completely right, I'll delete that 👍
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.
Approving with a couple of minor edits requested for casing consistency
| `level` | Level at which the option is defined | | ||
| `optname` | Name of the option being set | | ||
| `filter_len` | Length of the filter | | ||
| `filter` | Filter data | | ||
| `filter_hash` | Filter Hash | |
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.
| `filter_hash` | Filter Hash | | |
| `filter_hash` | Filter hash | |
}, | ||
"filter_hash": { | ||
"type": "string", | ||
"description": "Filter Hash" |
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.
"description": "Filter Hash" | |
"description": "Filter hash" |
5058f9f
to
4bfc4be
Compare
b48c2d3
to
f4e6606
Compare
41f445b
to
4c721b4
Compare
4c721b4
to
1efbd65
Compare
What does this PR do?
Adds additional information and data related to the setsockopt hook.
Socket Information:
Filter Information:
In addition, this PR provides new helpers that can be used:
Motivation
To more accurately detect BPF doors, additional data was required from the setsockopt syscall. Specifically, we need to retrieve details about the socket to which the filter is attached, as well as key information from the filter itself. This data enables us to define more precise detection rules based on specific filter characteristics.
Describe how you validated your changes
The setsockopt test was updated to verify the tracking of the newly added information.
Possible Drawbacks / Trade-offs
Additional Notes