-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Store initialization errors for filters #38409
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
91513af
to
38c005e
Compare
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: cac5cbf Optimization Goals: ✅ Improvement(s) detected
|
perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
---|---|---|---|---|---|---|
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +2.22 | [+1.35, +3.10] | 1 | Logs |
➖ | tcp_syslog_to_blackhole | ingress throughput | +1.08 | [+1.02, +1.14] | 1 | Logs |
➖ | ddot_logs | memory utilization | +0.68 | [+0.59, +0.77] | 1 | Logs |
➖ | otlp_ingest_metrics | memory utilization | +0.18 | [-0.05, +0.40] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency | egress throughput | +0.07 | [-0.55, +0.69] | 1 | Logs |
➖ | file_to_blackhole_0ms_latency_http1 | egress throughput | +0.04 | [-0.55, +0.62] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency_linear_load | egress throughput | +0.03 | [-0.20, +0.27] | 1 | Logs |
➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.02 | [-0.57, +0.60] | 1 | Logs |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.02, +0.02] | 1 | Logs |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.31, +0.30] | 1 | Logs |
➖ | file_to_blackhole_100ms_latency | egress throughput | -0.02 | [-0.60, +0.56] | 1 | Logs |
➖ | file_to_blackhole_500ms_latency | egress throughput | -0.02 | [-0.64, +0.61] | 1 | Logs |
➖ | otlp_ingest_logs | memory utilization | -0.04 | [-0.16, +0.08] | 1 | Logs |
➖ | file_to_blackhole_300ms_latency | egress throughput | -0.04 | [-0.70, +0.62] | 1 | Logs |
➖ | quality_gate_idle | memory utilization | -0.11 | [-0.18, -0.04] | 1 | Logs bounds checks dashboard |
➖ | file_to_blackhole_0ms_latency_http2 | egress throughput | -0.11 | [-0.73, +0.51] | 1 | Logs |
➖ | ddot_metrics | memory utilization | -0.19 | [-0.29, -0.10] | 1 | Logs |
➖ | file_tree | memory utilization | -0.25 | [-0.36, -0.13] | 1 | Logs |
➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.37 | [-0.42, -0.33] | 1 | Logs |
➖ | quality_gate_idle_all_features | memory utilization | -0.53 | [-0.60, -0.46] | 1 | Logs bounds checks dashboard |
➖ | docker_containers_memory | memory utilization | -0.91 | [-1.06, -0.76] | 1 | Logs |
➖ | quality_gate_logs | % cpu utilization | -1.72 | [-4.45, +1.01] | 1 | Logs bounds checks dashboard |
✅ | docker_containers_cpu | % cpu utilization | -8.18 | [-11.16, -5.19] | 1 | Logs |
Bounds Checks: ❌ Failed
perf | experiment | bounds_check_name | replicates_passed | links |
---|---|---|---|---|
❌ | docker_containers_cpu | simple_check_run | 9/10 | |
✅ | docker_containers_memory | memory_usage | 10/10 | |
❌ | docker_containers_memory | simple_check_run | 8/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 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 lost_bytes: 10/10 replicas passed. Gate passed.
- quality_gate_logs, 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, 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.
Pull Request Overview
This PR adds support for capturing and exposing initialization errors when creating filter programs, allowing clients to inspect filter construction failures.
- Extended the
FilterProgram
interface andCELProgram
struct to store initialization errors. - Updated
createProgramFromOldFilters
to return errors and propagated them through catalog constructors. - Introduced
GetContainerFilterInitializationErrors
in the filter implementation and added tests for initialization error handling.
Reviewed Changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated no comments.
Show a summary per file
File | Description |
---|---|
comp/core/workloadfilter/program/common.go | Added GetInitializationErrors to the FilterProgram interface. |
comp/core/workloadfilter/program/cel_program.go | Stored initialization errors in CELProgram and implemented getter. |
comp/core/workloadfilter/impl/filter.go | Added GetContainerFilterInitializationErrors and helper function. |
comp/core/workloadfilter/impl/filter_test.go | Added unit tests for initialization error retrieval. |
comp/core/workloadfilter/def/utils.go | Added FlattenFilterSets utility. |
comp/core/workloadfilter/def/component.go | Exposed GetContainerFilterInitializationErrors on Component . |
comp/core/workloadfilter/catalog/utils.go | Changed createProgramFromOldFilters to return (cel.Program, error) . |
comp/core/workloadfilter/catalog/kube_service.go | Captured init errors in service CEL programs. |
comp/core/workloadfilter/catalog/kube_endpoints.go | Captured init errors in endpoints CEL programs. |
comp/core/workloadfilter/catalog/container.go | Captured init errors in container CEL programs. |
Comments suppressed due to low confidence (3)
comp/core/workloadfilter/def/component.go:22
- [nitpick] The parameter name
filter
is singular but represents a slice; consider renaming it tofilters
for clarity.
GetContainerFilterInitializationErrors(filter []ContainerFilter) []error
comp/core/workloadfilter/catalog/utils.go:25
- The code uses fmt.Errorf but the fmt package is not imported; add
import "fmt"
to the imports.
return nil, fmt.Errorf("error converting filters: %w", err)
comp/core/workloadfilter/def/utils.go:92
- [nitpick] Pre-calculate the total length of all filter sets and allocate
flattened
with a capacity to avoid multiple reallocations.
flattened := make([]T, 0)
/merge |
View all feedbacks in Devflow UI.
The expected merge time in
|
What does this PR do?
Stores initialization errors while parsing and creating the filter programs
Motivation
Clients in the Agent are interested whether or not the filters were successfully created, hence, we need to store and expose this information when applicable.
CONTP-845
Describe how you validated your changes
Unit tests
Possible Drawbacks / Trade-offs
N/A