-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Sopell/amlii 1449 add host tags to metrics with hosttags exp #22579
Sopell/amlii 1449 add host tags to metrics with hosttags exp #22579
Conversation
Host tags are added to all metrics when `expected_tags_duration` is configured. This matches the behavior of the logs agent.
Go Package Import DifferencesBaseline: cd5ef07
|
Bloop Bleep... Dogbot HereRegression Detector ResultsRun ID: a953ca9e-b83f-4718-bf91-0e8a9826175f Performance changes are noted in the perf column of each table:
Significant changes in experiment optimization goalsConfidence level: 90.00%
|
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
➖ | file_to_blackhole | % cpu utilization | +0.83 | [-5.75, +7.41] |
➖ | idle | memory utilization | +0.48 | [+0.46, +0.51] |
➖ | file_tree | memory utilization | -0.17 | [-0.24, -0.09] |
Fine details of change detection per experiment
perf | experiment | goal | Δ mean % | Δ mean % CI |
---|---|---|---|---|
❌ | dogstatsd_with_big_hosttags | % cpu utilization | +7.27 | [+5.80, +8.73] |
➖ | otel_to_otel_logs | ingress throughput | +3.56 | [+2.82, +4.29] |
➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | +2.22 | [+0.78, +3.67] |
➖ | file_to_blackhole | % cpu utilization | +0.83 | [-5.75, +7.41] |
➖ | idle | memory utilization | +0.48 | [+0.46, +0.51] |
➖ | process_agent_standard_check | memory utilization | +0.39 | [+0.35, +0.44] |
➖ | process_agent_real_time_mode | memory utilization | +0.29 | [+0.26, +0.33] |
➖ | process_agent_standard_check_with_stats | memory utilization | +0.14 | [+0.11, +0.18] |
➖ | tcp_syslog_to_blackhole | ingress throughput | +0.07 | [-0.00, +0.13] |
➖ | trace_agent_json | ingress throughput | +0.03 | [+0.00, +0.06] |
➖ | tcp_dd_logs_filter_exclude | ingress throughput | +0.00 | [-0.06, +0.06] |
➖ | uds_dogstatsd_to_api | ingress throughput | -0.00 | [-0.03, +0.03] |
➖ | trace_agent_msgpack | ingress throughput | -0.02 | [-0.04, -0.01] |
➖ | file_tree | memory utilization | -0.17 | [-0.24, -0.09] |
Explanation
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".
Testing completed. As expected there is a perf impact for the initial duration where host tags are sent in each payload, after which we drop to a normal level. |
What does this PR do?
Testing the impact of #22467
Will not merge this, only used to run CI.
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Reviewer's Checklist
Triage
milestone is set.major_change
label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.changelog/no-changelog
label has been applied.qa/skip-qa
label, with required eitherqa/done
orqa/no-code-change
labels, are applied.team/..
label has been applied, indicating the team(s) that should QA this change.need-change/operator
andneed-change/helm
labels have been applied.k8s/<min-version>
label, indicating the lowest Kubernetes version compatible with this feature.