[APM] add implementation of span derived primary tags for APM stats#42996
Conversation
Static quality checks✅ Please find below the results from static quality gates Successful checksInfo
7 successful checks with minimal change (< 2 KiB)
On-wire sizes (compressed)
|
Regression DetectorRegression Detector ResultsMetrics dashboard Baseline: 9fd9c72 Optimization Goals: ✅ No significant changes detected
|
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_cpu | % cpu utilization | +1.51 | [-1.62, +4.64] | 1 | Logs |
Fine details of change detection per experiment
| perf | experiment | goal | Δ mean % | Δ mean % CI | trials | links |
|---|---|---|---|---|---|---|
| ➖ | docker_containers_memory | memory utilization | +1.56 | [+1.42, +1.70] | 1 | Logs |
| ➖ | docker_containers_cpu | % cpu utilization | +1.51 | [-1.62, +4.64] | 1 | Logs |
| ➖ | quality_gate_logs | % cpu utilization | +1.07 | [-0.45, +2.60] | 1 | Logs bounds checks dashboard |
| ➖ | tcp_syslog_to_blackhole | ingress throughput | +0.41 | [+0.33, +0.48] | 1 | Logs |
| ➖ | quality_gate_idle | memory utilization | +0.18 | [+0.13, +0.22] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_logs | memory utilization | +0.10 | [+0.04, +0.16] | 1 | Logs |
| ➖ | file_to_blackhole_1000ms_latency | egress throughput | +0.04 | [-0.39, +0.47] | 1 | Logs |
| ➖ | uds_dogstatsd_20mb_12k_contexts_20_senders | memory utilization | +0.03 | [-0.02, +0.08] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulativetodelta_exporter | memory utilization | +0.02 | [-0.21, +0.25] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api_v3 | ingress throughput | +0.01 | [-0.12, +0.13] | 1 | Logs |
| ➖ | file_to_blackhole_100ms_latency | egress throughput | +0.01 | [-0.04, +0.05] | 1 | Logs |
| ➖ | tcp_dd_logs_filter_exclude | ingress throughput | -0.00 | [-0.10, +0.09] | 1 | Logs |
| ➖ | uds_dogstatsd_to_api | ingress throughput | -0.01 | [-0.13, +0.11] | 1 | Logs |
| ➖ | file_to_blackhole_0ms_latency | egress throughput | -0.02 | [-0.50, +0.46] | 1 | Logs |
| ➖ | quality_gate_metrics_logs | memory utilization | -0.03 | [-0.23, +0.18] | 1 | Logs bounds checks dashboard |
| ➖ | otlp_ingest_metrics | memory utilization | -0.07 | [-0.22, +0.09] | 1 | Logs |
| ➖ | file_to_blackhole_500ms_latency | egress throughput | -0.08 | [-0.46, +0.30] | 1 | Logs |
| ➖ | ddot_metrics | memory utilization | -0.10 | [-0.32, +0.11] | 1 | Logs |
| ➖ | file_tree | memory utilization | -0.19 | [-0.24, -0.13] | 1 | Logs |
| ➖ | quality_gate_idle_all_features | memory utilization | -0.19 | [-0.23, -0.15] | 1 | Logs bounds checks dashboard |
| ➖ | ddot_metrics_sum_delta | memory utilization | -0.21 | [-0.40, -0.02] | 1 | Logs |
| ➖ | ddot_metrics_sum_cumulative | memory utilization | -0.50 | [-0.66, -0.34] | 1 | Logs |
| ➖ | otlp_ingest_logs | memory utilization | -0.62 | [-0.71, -0.52] | 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 | 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, bounds check intake_connections: 10/10 replicas passed. Gate passed.
- quality_gate_idle, 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_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_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_logs, 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.
|
All contributors have signed the CLA ✍️ ✅ |
a3a031d to
53e7aa2
Compare
|
I have read the CLA Document and I hereby sign the CLA |
| config.BindEnvAndSetDefault("apm_config.span_derived_primary_tags", []string{}, "DD_APM_SPAN_DERIVED_PRIMARY_TAGS") | ||
| config.ParseEnvAsStringSlice("apm_config.span_derived_primary_tags", func(in string) []string { | ||
| var out []string | ||
| if err := json.Unmarshal([]byte(in), &out); err != nil { |
There was a problem hiding this comment.
Just to verify this is what you want: if this setting is configured as an env var then the value has to be json. DD_APM_SPAN_DERIVED_PRIMARY_TAGS=key:value won't work, but DD_APM_SPAN_DERIVED_PRIMARY_TAGS=["key":"value"] will.
There was a problem hiding this comment.
This will only store the keys so DD_APM_SPAN_DERIVED_PRIMARY_TAGS='["key1","key2"]' is the intended behavior.
ichinaski
left a comment
There was a problem hiding this comment.
Leaving the PR approved, but there are a few follow ups needed for this new feature:
- Add a new revision to the Client-Side Stats spec
- Implement the required changes on the trace-agent to expose the new setting
- Implement the new feature on SDKs with CSS:
dd-trace-goanddd-trace-java,libdatadog - Add system-tests to verify the behavior and feature parity
bdcdd8c
into
main
…7] (#1630) # What does this PR do? Add two fields to `ClientGroupedStats`: 1. `service_source` 2. `span_derived_primary_tags` It syncs the changes on datadog-agent. See pkg/proto/datadog/trace/stats.proto in DataDog/datadog-agent#42996. # Motivation To support span derived primary tags for trace stats generated in Lambda extension. # Additional Notes @Sam-Maya is driving this effort. # How to test the change? This PR only includes struct changes in this PR. Will set and test the struct in future PRs. Co-authored-by: yiming.luo <[email protected]>
This feature adds configuration of span-based primary tags so that when APM stats are calculated, we collect the appropriate tags from spans. We cannot attach these tags in any other way.
Implementing this feature will help serverless customers who cannot rely on container tags for primary tags in APM. It will also help customers who have important span tags that can be used to scope their applications' performance.