-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Support Kafka actions via remote config with one-shot check execution #43325
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
Go Package Import DifferencesBaseline: f42d155
|
a78cd6e to
e60b3c8
Compare
e60b3c8 to
e82d30c
Compare
e82d30c to
a1ae377
Compare
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: f42d155 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +3.61 | [+0.62, +6.60] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +3.61 | [+0.62, +6.60] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +1.37 | [+1.30, +1.45] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | +1.00 | [+0.80, +1.20] | 1 | Logs |
| ➖ | docker_containers_memory | memory utilization | +0.55 | [+0.42, +0.69] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | +0.38 | [+0.32, +0.44] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | +0.29 | [+0.19, +0.38] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | +0.20 | [+0.05, +0.34] | 1 | Logs |
| ➖ | file_tree | memory utilization | +0.17 | [+0.12, +0.22] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | +0.15 | [-0.05, +0.36] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | +0.12 | [-0.09, +0.32] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.05 | [-0.00, +0.10] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.04 | [-0.20, +0.28] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | +0.03 | [-0.35, +0.41] | 1 | Logs |
| ➖ | otlp_ingest_metrics | memory utilization | +0.02 | [-0.12, +0.16] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.01 | [-0.04, +0.06] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.01 | [-0.07, +0.08] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.01 | [-0.11, +0.12] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.00 | [-0.12, +0.12] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.05 | [-0.46, +0.36] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.12 | [-0.49, +0.26] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | -0.17 | [-1.61, +1.28] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.38 | [-0.43, -0.34] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.42 | [-0.47, -0.37] | 1 | Logs bounds checks dashboard |
Bounds Checks: ✅ Passed
| perf | experiment | bounds_check_name | replicates_passed | links |
|---|---|---|---|---|
| ✅ | 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_1000ms_latency | lost_bytes | 10/10 | |
| ✅ | file_to_blackhole_1000ms_latency | 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_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 |
| ✅ | quality_gate_metrics_logs | cpu_usage | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | intake_connections | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_logs | lost_bytes | 10/10 | bounds checks dashboard |
| ✅ | quality_gate_metrics_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 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_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 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.
| ProductNDMDeviceProfilesCustom: {}, | ||
| ProductMetricControl: {}, | ||
| ProductDataStreamsLiveMessages: {}, | ||
| ProductDataStreamsKafkaActions: {}, |
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.
Out of an abundance of caution before the code freeze, let's please use the DEBUG product in this PR since the ProductDataStreamsKafkaActions staging keys haven't been created
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.
Ah okay, I see these don't affect the repo verification
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
### What does this PR do? Follow up to #43325 ### Motivation Events generated by the kafka_actions can easily be correlated with the action taken in the UI ### Describe how you validated your changes QA locally ### Additional Notes Co-authored-by: piotr.wolski <[email protected]>
### What does this PR do? Refactors the `kafka_actions` one-shot check implementation to use `run_once: true` + `Interval() == 0` instead of the `RunOnce()` interface, and removes all `RunOnce()` infrastructure that was added in #43325. **Key changes:** * Removed `RunOnce()` method from `check.Check` interface and all implementations * Python checks now support `run_once: true` in instance config, which sets `Interval()` to `0` * Checks with `Interval() == 0` use existing `enqueueOnce()` for immediate execution * Removed scheduler logic for de-scheduling `RunOnce()` checks * Fixed numeric precision issue: use `json.Decoder.UseNumber()` to prevent scientific notation (e.g., `1e+06`) in YAML ### Motivation After implementing #43325, I realized that the agent already had a mechanism for one-shot check execution: `Interval() == 0` triggers `enqueueOnce()` for immediate, single-run execution. The `RunOnce()` interface I added was: 1. **Redundant** - duplicated existing functionality 2. **Slower** - caused up to a 15-second delays due to bucket scheduling (checks were added to job queues instead of running immediately) 3. **More complex** - required interface changes across ~15 files ### Describe how you validated your changes * Manually tested with local agent - verified check executes immediately and only once (no more 15-second delay) Co-authored-by: piotr.wolski <[email protected]>
### What does this PR do? Refactors the `kafka_actions` one-shot check implementation to use `run_once: true` + `Interval() == 0` instead of the `RunOnce()` interface, and removes all `RunOnce()` infrastructure that was added in DataDog#43325. **Key changes:** * Removed `RunOnce()` method from `check.Check` interface and all implementations * Python checks now support `run_once: true` in instance config, which sets `Interval()` to `0` * Checks with `Interval() == 0` use existing `enqueueOnce()` for immediate execution * Removed scheduler logic for de-scheduling `RunOnce()` checks * Fixed numeric precision issue: use `json.Decoder.UseNumber()` to prevent scientific notation (e.g., `1e+06`) in YAML ### Motivation After implementing DataDog#43325, I realized that the agent already had a mechanism for one-shot check execution: `Interval() == 0` triggers `enqueueOnce()` for immediate, single-run execution. The `RunOnce()` interface I added was: 1. **Redundant** - duplicated existing functionality 2. **Slower** - caused up to a 15-second delays due to bucket scheduling (checks were added to job queues instead of running immediately) 3. **More complex** - required interface changes across ~15 files ### Describe how you validated your changes * Manually tested with local agent - verified check executes immediately and only once (no more 15-second delay) Co-authored-by: piotr.wolski <[email protected]> a560f83
What does this PR do?
Adds support for one-shot Kafka actions via remote configuration and introduces the
RunOnce()interface for checks that should be descheduled after their first execution.Key changes:
kafka_actionscheck scheduled via remote config (DSM_KAFKA_ACTIONS product) for one-off Kafka operationsRunOnce()method added tocheck.Checkinterface to support one-shot check executiontruefromRunOnce()after first runkafka_messagescontroller retained for backwards compatibilityMotivation
The existing
kafka_messagesfeature mutateskafka_consumerconfigs to add live message collection. This approach has limitations, as it modifies the existing kafka_consumer integration with a config that is only used once (it for example makes the kafka_consumer integration drop its cache, since the integration digest changes).kafka_actionsreplaces this with a more flexible approach: it schedules dedicated one-shot checks that execute a single action and are automatically removed from the scheduler. The check receives authentication details by matchingbootstrap_serversfrom existingkafka_consumerintegrations, ensuring correct cluster targeting.We keep
kafka_messagesuntil the frontend switches tokafka_actions.Describe how you validated your changes
kafka_actionscontroller (matching, auth extraction, config parsing)RunOnce()behaviorAdditional Notes
The
RunOnce()interface is generic and can be used by any check needing one-shot execution semantics (e.g., migration tasks, one-time configuration changes, etc.).