fix(dogstatsd): origin detection precedence for tag enrichment#41587
fix(dogstatsd): origin detection precedence for tag enrichment#41587dd-mergequeue[bot] merged 3 commits intomainfrom
Conversation
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 7936183 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ✅ | docker_containers_cpu | % cpu utilization | -11.68 | [-13.25, -10.12] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_memory | memory utilization | +3.38 | [+2.96, +3.81] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +1.99 | [-0.83, +4.82] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | +0.61 | [+0.49, +0.73] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.21 | [+0.17, +0.25] | 1 | Logs bounds checks dashboard |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | +0.04 | [-0.57, +0.65] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | +0.02 | [-0.22, +0.27] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.01, +0.01] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | -0.03 | [-0.65, +0.58] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | -0.04 | [-0.25, +0.17] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics | memory utilization | -0.04 | [-0.21, +0.12] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | -0.07 | [-0.26, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | -0.09 | [-0.70, +0.52] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.10 | [-0.14, -0.07] | 1 | Logs |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.12 | [-0.28, +0.03] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.13 | [-0.73, +0.46] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.25 | [-0.29, -0.22] | 1 | Logs bounds checks dashboard |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | -0.26 | [-0.32, -0.20] | 1 | Logs |
| ➖ | ddot_logs | memory utilization | -0.29 | [-0.35, -0.24] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.40 | [-0.51, -0.28] | 1 | Logs |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.56 | [-0.64, -0.47] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -1.06 | [-1.18, -0.94] | 1 | Logs |
| ✅ | docker_containers_cpu | % cpu utilization | -11.68 | [-13.25, -10.12] | 1 | Logs |
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 | 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_logs, 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_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 memory_usage: 10/10 replicas passed. Gate passed.
- quality_gate_idle_all_features, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check lost_bytes: 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 intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_metrics_logs, bounds check cpu_usage: 10/10 replicas passed. Gate passed.
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
|
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
### What does this PR do? Updates tag enrichment logic for unified Dogstatsd to enrich on only one entity ID, based on precedence. ### Motivation #incident-41903. During OOM kills on busy hosts, origin detection fails on rare occasion causing incorrect metric contexts being generated. To address these issues with duplicate/incorrect tag values from tag enrichment via origin detection, we’re changing the logic so that enrichment is based only on the highest-priority entity ID among all available IDs, rather than enriching separately on all container IDs and pod UIDs provided. Assuming that the provided containerID is correct, then all subsequent calls for tag accumulation on the "hypothetically" same containerID and podUID should return the same values. Therefore we can exit out from tag enrichment after the first hit. ### Describe how you validated your changes Unit tests and CI ### Additional Notes Removed the `OriginInfoContainerIDMismatch` because we will stop at the first valid containerID for tagging now. Thus, this metric does not provide value anymore in knowing whether we have incorrect tags on telemetry. It could still be useful for identifying other system issues with receiving faulty data related to ExternalData. For `GenerateContainerIDFromOriginInfo` we may want to consider also re-ordering the priority to use the Inode method as the second option and bumping down the more expensive and less reliable PIDtoCID method. Note, this doesn't affect DogStatsd, but rather other remote Agents that query the tagger such as trace-agent and process-agent. https://github.com/DataDog/datadog-agent/blob/fc2014a0f3c1a5a3df8736a6663f7ba90328ab65/comp/core/tagger/impl/tagger.go#L257-L269 (cherry picked from commit cceb7fc)
… enrichment (#41644) Backport cceb7fc from #41587. ___ ### What does this PR do? Updates tag enrichment logic for unified Dogstatsd to enrich on only one entity ID, based on precedence. ### Motivation #incident-41903. During OOM kills on busy hosts, origin detection fails on rare occasion causing incorrect metric contexts being generated. To address these issues with duplicate/incorrect tag values from tag enrichment via origin detection, we’re changing the logic so that enrichment is based only on the highest-priority entity ID among all available IDs, rather than enriching separately on all container IDs and pod UIDs provided. Assuming that the provided containerID is correct, then all subsequent calls for tag accumulation on the "hypothetically" same containerID and podUID should return the same values. Therefore we can exit out from tag enrichment after the first hit. ### Describe how you validated your changes Unit tests and CI ### Additional Notes Removed the `OriginInfoContainerIDMismatch` because we will stop at the first valid containerID for tagging now. Thus, this metric does not provide value anymore in knowing whether we have incorrect tags on telemetry. It could still be useful for identifying other system issues with receiving faulty data related to ExternalData. For `GenerateContainerIDFromOriginInfo` we may want to consider also re-ordering the priority to use the Inode method as the second option and bumping down the more expensive and less reliable PIDtoCID method. Note, this doesn't affect DogStatsd, but rather other remote Agents that query the tagger such as trace-agent and process-agent. https://github.com/DataDog/datadog-agent/blob/fc2014a0f3c1a5a3df8736a6663f7ba90328ab65/comp/core/tagger/impl/tagger.go#L257-L269 Co-authored-by: Gabriel Dos Santos <91925154+gabedos@users.noreply.github.com>
What does this PR do?
Updates tag enrichment logic for unified Dogstatsd to enrich on only one entity ID, based on precedence.
Motivation
#incident-41903. During OOM kills on busy hosts, origin detection fails on rare occasion causing incorrect metric contexts being generated.
To address these issues with duplicate/incorrect tag values from tag enrichment via origin detection, we’re changing the logic so that enrichment is based only on the highest-priority entity ID among all available IDs, rather than enriching separately on all container IDs and pod UIDs provided.
Assuming that the provided containerID is correct, then all subsequent calls for tag accumulation on the "hypothetically" same containerID and podUID should return the same values. Therefore we can exit out from tag enrichment after the first hit.
Describe how you validated your changes
Unit tests and CI
Additional Notes
Removed the
OriginInfoContainerIDMismatchbecause we will stop at the first valid containerID for tagging now. Thus, this metric does not provide value anymore in knowing whether we have incorrect tags on telemetry. It could still be useful for identifying other system issues with receiving faulty data related to ExternalData.For
GenerateContainerIDFromOriginInfowe may want to consider also re-ordering the priority to use the Inode method as the second option and bumping down the more expensive and less reliable PIDtoCID method. Note, this doesn't affect DogStatsd, but rather other remote Agents that query the tagger such as trace-agent and process-agent.datadog-agent/comp/core/tagger/impl/tagger.go
Lines 257 to 269 in fc2014a