datadog-agent
datadog-agent copied to clipboard
Expose config
What does this PR do?
Makes the config for serializerexporter public so that we can reuse it in the OSS collector. The PR also updates the collector version.
Motivation
Additional Notes
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Send OTLP data to Agent and verify we are able to receive them in DD backend.
Regression Detector
Regression Detector Results
Run ID: 1a98e9a1-dc0f-4b12-9174-a8e437b6ebeb Baseline: 28545c52d0ebf1b1039d95236c7a794f87165552 Comparison: 4bb7bfd005213905a3c2456dfc94ac88df5f5f44
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
No significant changes in experiment optimization goals
Confidence level: 90.00% Effect size tolerance: |Δ mean %| ≥ 5.00%
There were no significant changes in experiment optimization goals at this confidence level and effect size tolerance.
Experiments ignored for regressions
Regressions in experiments with settings containing erratic: true are ignored.
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | file_to_blackhole | % cpu utilization | -0.57 | [-6.92, +5.78] |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI |
|---|---|---|---|---|
| ➖ | pycheck_1000_100byte_tags | % cpu utilization | +1.99 | [-2.92, +6.91] |
| ➖ | file_tree | memory utilization | +0.52 | [+0.43, +0.61] |
| ➖ | otel_to_otel_logs | ingress throughput | +0.01 | [-0.42, +0.44] |
| ➖ | trace_agent_msgpack | ingress throughput | +0.00 | [-0.00, +0.00] |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.01 | [-0.02, +0.01] |
| ➖ | trace_agent_json | ingress throughput | -0.02 | [-0.04, +0.01] |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.02 | [-0.22, +0.19] |
| ➖ | process_agent_standard_check | memory utilization | -0.11 | [-0.14, -0.08] |
| ➖ | idle | memory utilization | -0.20 | [-0.23, -0.17] |
| ➖ | process_agent_standard_check_with_stats | memory utilization | -0.30 | [-0.33, -0.27] |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | -0.45 | [-0.54, -0.36] |
| ➖ | file_to_blackhole | % cpu utilization | -0.57 | [-6.92, +5.78] |
| ➖ | process_agent_real_time_mode | memory utilization | -0.73 | [-0.77, -0.70] |
| ➖ | uds_dogstatsd_to_api_cpu | % cpu utilization | -0.82 | [-3.57, +1.94] |
| ➖ | basic_py_check | % cpu utilization | -2.28 | [-4.60, +0.04] |
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".
Test changes on VM
Use this command from test-infra-definitions to manually test this PR changes on a VM:
inv create-vm --pipeline-id=30261500 --os-family=ubuntu
/merge
:steam_locomotive: MergeQueue
Pull request added to the queue.
This build is next! (estimated merge in less than 28m)
Use /merge -c to cancel this operation!