Skip to content

fix(trace-stats): cardinality limit telemetry name - #2559

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits into
mainfrom
oscarld/fix-cardinality-limit-telemetry
Sep 22, 2026
Merged

fix(trace-stats): cardinality limit telemetry name#2559
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits into
mainfrom
oscarld/fix-cardinality-limit-telemetry

Conversation

@Eldolfin

@Eldolfin Eldolfin commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

What does this PR do?

  • fixes stats_collapsed_spans telemetry name: tracers.stats_collapsed_spans -> stats_collapsed_spans (tracer is already the namespace)
  • fixes collapsed tag name for both telemetry and health metrics: collapsed_spans -> collapsed

Motivation

When trying out CSS cardinality limit telemetry, none was showing up in the CSS rollout dashboard

Additional Notes

Anything else we should know when reviewing?

How to test the change?

Describe here in detail how the change can be validated.

@pr-commenter

pr-commenter Bot commented Sep 22, 2026 •
edited
Loading

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-09-22 15:00:40

Comparing candidate commit bbab584 in PR branch oscarld/fix-cardinality-limit-telemetry with baseline commit fed3d2e in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 24 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Benchmark execution time: 2026-09-22 14:56:48

Comparing candidate commit bbab584 in PR branch oscarld/fix-cardinality-limit-telemetry with baseline commit fed3d2e in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 3 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

  • 🟩 = significantly better candidate vs. baseline
  • 🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

Candidate

Candidate benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz bbab584 1790088460 oscarld/fix-cardinality-limit-telemetry
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
trace_buffer/1_senders/10us_delay execution_time 59.868ms 59.981ms ± 0.030ms 59.975ms ± 0.007ms 59.982ms 60.036ms 60.119ms 60.155ms 0.30% 2.700 13.136 0.05% 0.002ms 1 200
trace_buffer/1_senders/10us_delay throughput 14961.281op/s 15004.838op/s ± 7.608op/s 15006.212op/s ± 1.740op/s 15007.963op/s 15011.026op/s 15013.178op/s 15033.132op/s 0.18% -2.688 13.082 0.05% 0.538op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.054ms 50.515ms ± 0.312ms 50.455ms ± 0.237ms 50.760ms 51.085ms 51.135ms 51.235ms 1.55% 0.468 -0.919 0.62% 0.022ms 1 200
trace_buffer/1_senders/1us_delay throughput 17566.096op/s 17817.185op/s ± 109.611op/s 17837.568op/s ± 83.566op/s 17907.853op/s 17960.636op/s 17976.470op/s 17980.622op/s 0.80% -0.452 -0.937 0.61% 7.751op/s 1 200
trace_buffer/1_senders/no_delay execution_time 338.203µs 339.679µs ± 0.769µs 339.577µs ± 0.342µs 339.957µs 340.684µs 341.186µs 347.156µs 2.23% 4.663 43.019 0.23% 0.054µs 1 200
trace_buffer/1_senders/no_delay throughput 2592495.886op/s 2649575.053op/s ± 5937.043op/s 2650354.164op/s ± 2672.585op/s 2652458.175op/s 2656602.012op/s 2660088.148op/s 2661124.914op/s 0.41% -4.508 41.070 0.22% 419.812op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 59.908ms 60.000ms ± 0.040ms 59.988ms ± 0.013ms 60.007ms 60.054ms 60.166ms 60.221ms 0.39% 2.600 8.746 0.07% 0.003ms 1 200
trace_buffer/2_senders/10us_delay throughput 29889.711op/s 29999.900op/s ± 19.789op/s 30005.820op/s ± 6.267op/s 30010.934op/s 30016.871op/s 30018.835op/s 30045.890op/s 0.13% -2.592 8.698 0.07% 1.399op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 50.730ms 51.084ms ± 0.085ms 51.080ms ± 0.047ms 51.129ms 51.219ms 51.249ms 51.413ms 0.65% -0.261 1.953 0.17% 0.006ms 1 200
trace_buffer/2_senders/1us_delay throughput 35010.511op/s 35236.363op/s ± 58.807op/s 35238.755op/s ± 32.670op/s 35263.507op/s 35340.611op/s 35375.842op/s 35481.642op/s 0.69% 0.281 1.964 0.17% 4.158op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.525ms 1.654ms ± 0.035ms 1.662ms ± 0.023ms 1.680ms 1.705ms 1.716ms 1.717ms 3.32% -0.618 0.337 2.10% 0.002ms 1 200
trace_buffer/2_senders/no_delay throughput 1048486.257op/s 1088912.289op/s ± 23311.164op/s 1083263.976op/s ± 15207.277op/s 1105107.145op/s 1128036.960op/s 1156149.545op/s 1180557.245op/s 8.98% 0.748 0.690 2.14% 1648.348op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 59.983ms 60.032ms ± 0.030ms 60.030ms ± 0.014ms 60.042ms 60.075ms 60.143ms 60.189ms 0.26% 2.119 6.916 0.05% 0.002ms 1 200
trace_buffer/4_senders/10us_delay throughput 59811.892op/s 59968.281op/s ± 29.514op/s 59970.209op/s ± 14.048op/s 59986.605op/s 60004.439op/s 60008.905op/s 60017.308op/s 0.08% -2.112 6.881 0.05% 2.087op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.051ms 51.328ms ± 0.130ms 51.316ms ± 0.084ms 51.406ms 51.548ms 51.672ms 51.751ms 0.85% 0.540 0.254 0.25% 0.009ms 1 200
trace_buffer/4_senders/1us_delay throughput 69563.262op/s 70137.522op/s ± 177.462op/s 70153.452op/s ± 114.420op/s 70263.324op/s 70393.793op/s 70495.008op/s 70517.769op/s 0.52% -0.526 0.227 0.25% 12.548op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.446ms 3.513ms ± 0.022ms 3.515ms ± 0.015ms 3.527ms 3.548ms 3.567ms 3.569ms 1.55% -0.144 0.165 0.64% 0.002ms 1 200
trace_buffer/4_senders/no_delay throughput 1008613.673op/s 1024682.185op/s ± 6542.395op/s 1024296.338op/s ± 4386.042op/s 1029106.667op/s 1035737.180op/s 1041229.550op/s 1044618.682op/s 1.98% 0.185 0.190 0.64% 462.617op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 59.996ms 60.083ms ± 0.059ms 60.065ms ± 0.028ms 60.113ms 60.204ms 60.243ms 60.323ms 0.43% 1.219 1.237 0.10% 0.004ms 1 200
trace_buffer/8_senders/10us_delay throughput 119357.615op/s 119834.393op/s ± 117.465op/s 119870.477op/s ± 55.492op/s 119917.791op/s 119968.431op/s 119995.855op/s 120008.735op/s 0.12% -1.214 1.218 0.10% 8.306op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.458ms 51.854ms ± 0.189ms 51.823ms ± 0.114ms 51.956ms 52.195ms 52.371ms 52.626ms 1.55% 0.903 0.842 0.36% 0.013ms 1 200
trace_buffer/8_senders/1us_delay throughput 136815.464op/s 138853.025op/s ± 504.968op/s 138934.240op/s ± 305.152op/s 139229.487op/s 139520.161op/s 139596.226op/s 139919.089op/s 0.71% -0.881 0.773 0.36% 35.707op/s 1 200
trace_buffer/8_senders/no_delay execution_time 6.617ms 6.710ms ± 0.032ms 6.708ms ± 0.021ms 6.730ms 6.765ms 6.793ms 6.805ms 1.45% 0.277 0.094 0.48% 0.002ms 1 200
trace_buffer/8_senders/no_delay throughput 1057968.546op/s 1073023.084op/s ± 5159.388op/s 1073315.473op/s ± 3377.046op/s 1076297.765op/s 1080470.499op/s 1083479.981op/s 1088060.570op/s 1.37% -0.248 0.079 0.48% 364.824op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
trace_buffer/1_senders/10us_delay execution_time [59.976ms; 59.985ms] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/10us_delay throughput [15003.783op/s; 15005.892op/s] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.472ms; 50.558ms] or [-0.086%; +0.086%] None None None
trace_buffer/1_senders/1us_delay throughput [17801.994op/s; 17832.376op/s] or [-0.085%; +0.085%] None None None
trace_buffer/1_senders/no_delay execution_time [339.572µs; 339.785µs] or [-0.031%; +0.031%] None None None
trace_buffer/1_senders/no_delay throughput [2648752.236op/s; 2650397.870op/s] or [-0.031%; +0.031%] None None None
trace_buffer/2_senders/10us_delay execution_time [59.995ms; 60.006ms] or [-0.009%; +0.009%] None None None
trace_buffer/2_senders/10us_delay throughput [29997.157op/s; 30002.642op/s] or [-0.009%; +0.009%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.072ms; 51.096ms] or [-0.023%; +0.023%] None None None
trace_buffer/2_senders/1us_delay throughput [35228.213op/s; 35244.513op/s] or [-0.023%; +0.023%] None None None
trace_buffer/2_senders/no_delay execution_time [1.649ms; 1.659ms] or [-0.292%; +0.292%] None None None
trace_buffer/2_senders/no_delay throughput [1085681.586op/s; 1092142.993op/s] or [-0.297%; +0.297%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.028ms; 60.036ms] or [-0.007%; +0.007%] None None None
trace_buffer/4_senders/10us_delay throughput [59964.190op/s; 59972.371op/s] or [-0.007%; +0.007%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.310ms; 51.346ms] or [-0.035%; +0.035%] None None None
trace_buffer/4_senders/1us_delay throughput [70112.928op/s; 70162.117op/s] or [-0.035%; +0.035%] None None None
trace_buffer/4_senders/no_delay execution_time [3.510ms; 3.517ms] or [-0.088%; +0.088%] None None None
trace_buffer/4_senders/no_delay throughput [1023775.472op/s; 1025588.898op/s] or [-0.088%; +0.088%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.075ms; 60.091ms] or [-0.014%; +0.014%] None None None
trace_buffer/8_senders/10us_delay throughput [119818.113op/s; 119850.672op/s] or [-0.014%; +0.014%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.828ms; 51.880ms] or [-0.051%; +0.051%] None None None
trace_buffer/8_senders/1us_delay throughput [138783.041op/s; 138923.009op/s] or [-0.050%; +0.050%] None None None
trace_buffer/8_senders/no_delay execution_time [6.706ms; 6.715ms] or [-0.067%; +0.067%] None None None
trace_buffer/8_senders/no_delay throughput [1072308.043op/s; 1073738.126op/s] or [-0.067%; +0.067%] None None None

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz bbab584 1790088460 oscarld/fix-cardinality-limit-telemetry
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
two way interface execution_time 15.435µs 15.770µs ± 0.185µs 15.749µs ± 0.094µs 15.850µs 16.023µs 16.301µs 17.271µs 9.66% 3.072 20.703 1.17% 0.013µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
two way interface execution_time [15.744µs; 15.796µs] or [-0.163%; +0.163%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz bbab584 1790088460 oscarld/fix-cardinality-limit-telemetry
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
write only interface execution_time 1.060µs 1.085µs ± 0.007µs 1.085µs ± 0.006µs 1.091µs 1.095µs 1.097µs 1.099µs 1.29% -0.519 0.055 0.66% 0.001µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
write only interface execution_time [1.084µs; 1.086µs] or [-0.092%; +0.092%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz bbab584 1790088460 oscarld/fix-cardinality-limit-telemetry
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
concentrator/add_spans_to_concentrator execution_time 9.538ms 9.566ms ± 0.017ms 9.563ms ± 0.011ms 9.575ms 9.596ms 9.626ms 9.630ms 0.71% 1.012 1.353 0.18% 0.001ms 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
concentrator/add_spans_to_concentrator execution_time [9.563ms; 9.568ms] or [-0.025%; +0.025%] None None None

Baseline

Baseline benchmark details

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz fed3d2e 1790088148 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
trace_buffer/1_senders/10us_delay execution_time 59.835ms 59.985ms ± 0.031ms 59.981ms ± 0.007ms 59.988ms 60.043ms 60.117ms 60.131ms 0.25% 1.351 11.363 0.05% 0.002ms 1 200
trace_buffer/1_senders/10us_delay throughput 14967.298op/s 15003.796op/s ± 7.717op/s 15004.814op/s ± 1.836op/s 15006.629op/s 15009.425op/s 15018.560op/s 15041.276op/s 0.24% -1.333 11.364 0.05% 0.546op/s 1 200
trace_buffer/1_senders/1us_delay execution_time 50.070ms 50.449ms ± 0.193ms 50.416ms ± 0.152ms 50.589ms 50.785ms 50.884ms 50.933ms 1.03% 0.271 -0.743 0.38% 0.014ms 1 200
trace_buffer/1_senders/1us_delay throughput 17670.121op/s 17840.153op/s ± 68.174op/s 17851.422op/s ± 53.820op/s 17896.101op/s 17943.238op/s 17963.594op/s 17974.787op/s 0.69% -0.257 -0.753 0.38% 4.821op/s 1 200
trace_buffer/1_senders/no_delay execution_time 339.303µs 340.515µs ± 1.026µs 340.414µs ± 0.392µs 340.784µs 341.413µs 342.375µs 352.480µs 3.54% 8.090 90.978 0.30% 0.073µs 1 200
trace_buffer/1_senders/no_delay throughput 2553334.023op/s 2643078.593op/s ± 7774.798op/s 2643840.562op/s ± 3049.754op/s 2646918.128op/s 2649829.052op/s 2651632.520op/s 2652496.693op/s 0.33% -7.845 87.120 0.29% 549.761op/s 1 200
trace_buffer/2_senders/10us_delay execution_time 59.917ms 59.998ms ± 0.032ms 59.991ms ± 0.011ms 60.004ms 60.054ms 60.127ms 60.172ms 0.30% 2.391 8.646 0.05% 0.002ms 1 200
trace_buffer/2_senders/10us_delay throughput 29914.278op/s 30000.893op/s ± 16.024op/s 30004.616op/s ± 5.513op/s 30009.236op/s 30015.777op/s 30019.273op/s 30041.807op/s 0.12% -2.383 8.607 0.05% 1.133op/s 1 200
trace_buffer/2_senders/1us_delay execution_time 50.663ms 51.059ms ± 0.090ms 51.069ms ± 0.056ms 51.118ms 51.181ms 51.230ms 51.332ms 0.51% -0.656 1.671 0.18% 0.006ms 1 200
trace_buffer/2_senders/1us_delay throughput 35065.933op/s 35253.706op/s ± 62.345op/s 35246.484op/s ± 38.713op/s 35288.586op/s 35362.679op/s 35421.081op/s 35528.981op/s 0.80% 0.673 1.715 0.18% 4.408op/s 1 200
trace_buffer/2_senders/no_delay execution_time 1.617ms 1.702ms ± 0.032ms 1.705ms ± 0.023ms 1.726ms 1.753ms 1.769ms 1.775ms 4.09% -0.289 -0.218 1.88% 0.002ms 1 200
trace_buffer/2_senders/no_delay throughput 1014105.303op/s 1057873.501op/s ± 20057.208op/s 1055599.891op/s ± 14212.060op/s 1071335.691op/s 1094848.823op/s 1109575.408op/s 1112831.122op/s 5.42% 0.385 -0.139 1.89% 1418.259op/s 1 200
trace_buffer/4_senders/10us_delay execution_time 59.944ms 60.033ms ± 0.038ms 60.025ms ± 0.017ms 60.045ms 60.117ms 60.167ms 60.230ms 0.34% 1.958 5.751 0.06% 0.003ms 1 200
trace_buffer/4_senders/10us_delay throughput 59770.551op/s 59967.009op/s ± 37.938op/s 59975.320op/s ± 17.325op/s 59989.364op/s 60010.743op/s 60018.299op/s 60055.741op/s 0.13% -1.950 5.715 0.06% 2.683op/s 1 200
trace_buffer/4_senders/1us_delay execution_time 51.001ms 51.297ms ± 0.170ms 51.253ms ± 0.084ms 51.372ms 51.578ms 51.822ms 52.443ms 2.32% 2.408 10.918 0.33% 0.012ms 1 200
trace_buffer/4_senders/1us_delay throughput 68646.129op/s 70180.169op/s ± 230.646op/s 70239.545op/s ± 115.369op/s 70337.330op/s 70420.625op/s 70472.290op/s 70586.879op/s 0.49% -2.339 10.339 0.33% 16.309op/s 1 200
trace_buffer/4_senders/no_delay execution_time 3.437ms 3.508ms ± 0.024ms 3.507ms ± 0.014ms 3.521ms 3.548ms 3.569ms 3.582ms 2.13% 0.041 0.429 0.69% 0.002ms 1 200
trace_buffer/4_senders/no_delay throughput 1005122.663op/s 1026309.895op/s ± 7117.901op/s 1026498.781op/s ± 4150.485op/s 1030722.781op/s 1038086.744op/s 1044039.075op/s 1047412.281op/s 2.04% 0.010 0.436 0.69% 503.312op/s 1 200
trace_buffer/8_senders/10us_delay execution_time 59.999ms 60.089ms ± 0.058ms 60.070ms ± 0.030ms 60.131ms 60.192ms 60.258ms 60.273ms 0.34% 0.975 0.549 0.10% 0.004ms 1 200
trace_buffer/8_senders/10us_delay throughput 119456.110op/s 119823.174op/s ± 114.649op/s 119860.189op/s ± 60.385op/s 119902.379op/s 119966.141op/s 119992.179op/s 120002.010op/s 0.12% -0.970 0.537 0.10% 8.107op/s 1 200
trace_buffer/8_senders/1us_delay execution_time 51.461ms 51.846ms ± 0.256ms 51.780ms ± 0.149ms 52.000ms 52.340ms 52.591ms 52.623ms 1.63% 0.932 0.199 0.49% 0.018ms 1 200
trace_buffer/8_senders/1us_delay throughput 136822.411op/s 138877.128op/s ± 681.482op/s 139049.558op/s ± 399.404op/s 139383.419op/s 139718.823op/s 139836.102op/s 139910.886op/s 0.62% -0.912 0.152 0.49% 48.188op/s 1 200
trace_buffer/8_senders/no_delay execution_time 6.500ms 6.575ms ± 0.031ms 6.578ms ± 0.022ms 6.594ms 6.620ms 6.638ms 6.683ms 1.60% 0.011 0.141 0.46% 0.002ms 1 200
trace_buffer/8_senders/no_delay throughput 1077281.426op/s 1095046.720op/s ± 5102.731op/s 1094495.222op/s ± 3640.523op/s 1098712.321op/s 1103836.057op/s 1106157.734op/s 1107751.331op/s 1.21% 0.018 0.112 0.46% 360.818op/s 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
trace_buffer/1_senders/10us_delay execution_time [59.981ms; 59.989ms] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/10us_delay throughput [15002.727op/s; 15004.866op/s] or [-0.007%; +0.007%] None None None
trace_buffer/1_senders/1us_delay execution_time [50.422ms; 50.475ms] or [-0.053%; +0.053%] None None None
trace_buffer/1_senders/1us_delay throughput [17830.704op/s; 17849.601op/s] or [-0.053%; +0.053%] None None None
trace_buffer/1_senders/no_delay execution_time [340.373µs; 340.657µs] or [-0.042%; +0.042%] None None None
trace_buffer/1_senders/no_delay throughput [2642001.081op/s; 2644156.105op/s] or [-0.041%; +0.041%] None None None
trace_buffer/2_senders/10us_delay execution_time [59.994ms; 60.003ms] or [-0.007%; +0.007%] None None None
trace_buffer/2_senders/10us_delay throughput [29998.672op/s; 30003.114op/s] or [-0.007%; +0.007%] None None None
trace_buffer/2_senders/1us_delay execution_time [51.046ms; 51.071ms] or [-0.024%; +0.024%] None None None
trace_buffer/2_senders/1us_delay throughput [35245.066op/s; 35262.347op/s] or [-0.025%; +0.025%] None None None
trace_buffer/2_senders/no_delay execution_time [1.698ms; 1.707ms] or [-0.261%; +0.261%] None None None
trace_buffer/2_senders/no_delay throughput [1055093.765op/s; 1060653.237op/s] or [-0.263%; +0.263%] None None None
trace_buffer/4_senders/10us_delay execution_time [60.028ms; 60.038ms] or [-0.009%; +0.009%] None None None
trace_buffer/4_senders/10us_delay throughput [59961.751op/s; 59972.267op/s] or [-0.009%; +0.009%] None None None
trace_buffer/4_senders/1us_delay execution_time [51.274ms; 51.321ms] or [-0.046%; +0.046%] None None None
trace_buffer/4_senders/1us_delay throughput [70148.204op/s; 70212.134op/s] or [-0.046%; +0.046%] None None None
trace_buffer/4_senders/no_delay execution_time [3.505ms; 3.511ms] or [-0.096%; +0.096%] None None None
trace_buffer/4_senders/no_delay throughput [1025323.423op/s; 1027296.368op/s] or [-0.096%; +0.096%] None None None
trace_buffer/8_senders/10us_delay execution_time [60.081ms; 60.097ms] or [-0.013%; +0.013%] None None None
trace_buffer/8_senders/10us_delay throughput [119807.285op/s; 119839.064op/s] or [-0.013%; +0.013%] None None None
trace_buffer/8_senders/1us_delay execution_time [51.810ms; 51.881ms] or [-0.068%; +0.068%] None None None
trace_buffer/8_senders/1us_delay throughput [138782.682op/s; 138971.575op/s] or [-0.068%; +0.068%] None None None
trace_buffer/8_senders/no_delay execution_time [6.571ms; 6.579ms] or [-0.065%; +0.065%] None None None
trace_buffer/8_senders/no_delay throughput [1094339.531op/s; 1095753.910op/s] or [-0.065%; +0.065%] None None None

Group 1

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fed3d2e 1790088148 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
two way interface execution_time 15.770µs 16.098µs ± 0.140µs 16.087µs ± 0.099µs 16.188µs 16.349µs 16.448µs 16.510µs 2.63% 0.376 -0.095 0.87% 0.010µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
two way interface execution_time [16.079µs; 16.118µs] or [-0.120%; +0.120%] None None None

Group 2

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fed3d2e 1790088148 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
write only interface execution_time 1.061µs 1.077µs ± 0.006µs 1.077µs ± 0.004µs 1.082µs 1.085µs 1.088µs 1.089µs 1.08% -0.578 -0.336 0.58% 0.000µs 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
write only interface execution_time [1.076µs; 1.078µs] or [-0.081%; +0.081%] None None None

Group 3

cpu_model git_commit_sha git_commit_date git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz fed3d2e 1790088148 main
scenario metric min mean ± sd median ± mad p75 p95 p99 max peak_to_median_ratio skewness kurtosis cv sem runs sample_size
concentrator/add_spans_to_concentrator execution_time 9.515ms 9.542ms ± 0.017ms 9.538ms ± 0.010ms 9.553ms 9.576ms 9.592ms 9.595ms 0.60% 0.975 0.429 0.18% 0.001ms 1 200
scenario metric 95% CI mean Shapiro-Wilk pvalue Ljung-Box pvalue (lag=1) Dip test pvalue
concentrator/add_spans_to_concentrator execution_time [9.540ms; 9.545ms] or [-0.025%; +0.025%] None None None

VianneyRuhlmann
VianneyRuhlmann approved these changes Sep 22, 2026
View reviewed changes

@VianneyRuhlmann VianneyRuhlmann left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch

@Eldolfin
Eldolfin marked this pull request as ready for review September 22, 2026 14:56
@Eldolfin
Eldolfin requested a review from a team as a code owner September 22, 2026 14:56
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 22, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-09-22T14:58:02.011565Z bbab584 Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@datadog-datadog-prod-us1

datadog-datadog-prod-us1 Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Tests

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 77.78%
• Overall Coverage: 78.06% (-0.03%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: bbab584 | Docs | View more details | Give us feedback!

This was referenced Sep 22, 2026
Merged
Merged
@dd-octo-sts

dd-octo-sts Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 95.92 MB 95.92 MB -0% (-328 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 9.02 MB 9.02 MB 0% (0 B) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 12.19 MB 12.19 MB -0% (-72 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 107.30 MB 107.30 MB -0% (-288 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll 29.06 MB 29.06 MB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb 191.44 MB 191.43 MB -0% (-16.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib 816.66 MB 816.66 MB -0% (-40 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll 9.70 MB 9.70 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib 96.08 KB 96.08 KB 0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb 27.49 MB 27.49 MB 0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib 55.57 MB 55.57 MB -0% (-46 B) 👌
libdatadog-x86-windows
Artifact Baseline Commit Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll 25.41 MB 25.41 MB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb 196.65 MB 196.67 MB +.01% (+24.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib 802.18 MB 802.18 MB -0% (-44 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll 7.52 MB 7.52 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib 97.58 KB 97.58 KB 0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb 29.60 MB 29.60 MB 0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib 52.52 MB 52.52 MB -0% (-44 B) 👌
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 85.92 MB 85.92 MB -0% (-272 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 10.04 MB 10.04 MB 0% (0 B) 👌
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 101.79 MB 101.79 MB -0% (-368 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 12.26 MB 12.26 MB 0% (0 B) 👌

@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 30d0ea7 into main Sep 22, 2026
124 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the oscarld/fix-cardinality-limit-telemetry branch September 22, 2026 16:07
gh-worker-dd-mergequeue-cf854d Bot pushed a commit that referenced this pull request Sep 23, 2026
@Eldolfin
fix(trace-stats)!: cardinality limit telemetry name (v44 backport) (#…
c6414b2 
…2561)

# What does this PR do?
Backport #2559 to v44.

# Motivation

What inspired you to submit this pull request?

# Additional Notes

Note the breaking change marker in the title is misleading, but the semver check seems to not compare with the good base (TODO: fix it).

# How to test the change?

Describe here in detail how the change can be validated.


Co-authored-by: oscar.ledauphin <oscar.ledauphin@datadoghq.com>
gh-worker-dd-mergequeue-cf854d Bot pushed a commit that referenced this pull request Sep 23, 2026
@Eldolfin
fix(trace-stats)!: cardinality limit telemetry name (v43 backport) (#…
2f0d274 
…2560)

# What does this PR do?

Backport #2559 to v43.

# Motivation

What inspired you to submit this pull request?

# Additional Notes

Note the breaking change marker in the title is misleading, but the semver check seems to not compare with the good base (TODO: fix it).

# How to test the change?

Describe here in detail how the change can be validated.


Co-authored-by: oscar.ledauphin <oscar.ledauphin@datadoghq.com>
@dd-octo-sts dd-octo-sts Bot mentioned this pull request Sep 24, 2026
Merged
paullegranddc added a commit that referenced this pull request Sep 24, 2026
@dd-octo-sts @github-actions @paullegranddc
chore(release): proposal for libdd-capabilities-impl, libdd-common, l…
6163add 
…ibdd-data-pipeline, libdd-li... (#2571)

<!-- release-proposal-inputs: {"crates":"libdd-capabilities-impl,
libdd-common, libdd-data-pipeline, libdd-library-config,
libdd-profiling-heap-allocator, libdd-remote-config, libdd-sampling,
libdd-shared-runtime, libdd-telemetry, libdd-tinybytes,
libdd-trace-utils","main_start_ref":"","level_overrides":"","bypass_standard_checks":false}
-->

# Release proposal for libdd-capabilities-impl, libdd-common,
libdd-data-pipeline, libdd-library-config,
libdd-profiling-heap-allocator, libdd-remote-config, libdd-sampling,
libdd-shared-runtime, libdd-telemetry, libdd-tinybytes,
libdd-trace-utils and their dependencies

This PR contains version bumps based on public API changes and commits
since last release.


### ⚠️ Crates left out of this proposal affected by its major
bumps

These publishable workspace crates are not part of this release but
their dependency requirement was rewritten on this branch while their
published version still requires the old major. If they are a dependency
on your deployment not including them in the release could result in
duplicate packages or symbol incompatibility.

- `libdd-capabilities` `3.0.1` → `4.0.0` affects: `libdd-crashtracker`,
`libdd-ffe`, `libdd-live-debugger`
- `libdd-capabilities-impl` `5.0.0` → `6.0.0` affects:
`libdd-crashtracker`, `libdd-live-debugger`, `libdd-tracer-flare`
- `libdd-common` `6.0.0` → `7.0.0` affects: `libdd-crashtracker`,
`libdd-ffe`, `libdd-http-client`, `libdd-ipc`, `libdd-live-debugger`,
`libdd-profiling`, `libdd-tracer-flare`
- `libdd-data-pipeline` `10.0.0` → `11.0.0` affects:
`libdd-live-debugger`
- `libdd-remote-config` `5.0.0` → `6.0.0` affects: `libdd-ffe`,
`libdd-live-debugger`, `libdd-tracer-flare`
- `libdd-telemetry` `8.0.0` → `9.0.0` affects: `libdd-crashtracker`
- `libdd-trace-stats` `9.0.0` → `10.0.0` affects: `libdd-ipc`
- `libdd-trace-utils` `12.0.0` → `13.0.0` affects: `libdd-tracer-flare`

## libdd-capabilities
**Next version:** `4.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-v4.0.0`

### Commits

- feat(trace-exporter)!: add API to force flush stats on the trace
exporter (#2538)
- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-common
**Next version:** `7.0.0`
**Semver bump:** `major`
**Tag:** `libdd-common-v7.0.0`

### Commits

- build: enforce workspace-level dependency declarations (#2514)
- chore!: remove unused dependencies (v2) (#2511)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)
- fix!: benchmark was doing many samples for deterministic heap usage
(#2465)

## libdd-ddsketch
**Next version:** `1.1.2`
**Semver bump:** `patch`
**Tag:** `libdd-ddsketch-v1.1.2`

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)

## libdd-profiling-heap-sampler
**Next version:** `1.1.0`
**Semver bump:** `minor`
**Tag:** `libdd-profiling-heap-sampler-v1.1.0`

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- feat(profiling): add USDT semaphores to skip slow path around heap
profile sampler (#2266)

## libdd-tinybytes
**Next version:** `1.1.4`
**Semver bump:** `patch`
**Tag:** `libdd-tinybytes-v1.1.4`

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-trace-protobuf
**Next version:** `5.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-trace-protobuf-v5.0.1`

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- fix(build): build script change detection (#2467)

## libdd-capabilities-impl
**Next version:** `6.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-impl-v6.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0

### Commits

- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- fix(sidecar)!: stabilize the sidecar for macos usage (#2475)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-profiling-heap-allocator
**Next version:** `1.1.0`
**Semver bump:** `minor`
**Tag:** `libdd-profiling-heap-allocator-v1.1.0`

### Commits

- refactor(benchmarks): measure allocator thread CPU time (#2500)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- feat(profiling): add USDT semaphores to skip slow path around heap
profile sampler (#2266)

## libdd-library-config
**Next version:** `4.1.0`
**Semver bump:** `minor`
**Tag:** `libdd-library-config-v4.1.0`

### Commits

- chore!: remove unused dependencies (v2) (#2511)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-trace-normalization
**Next version:** `4.1.0`
**Semver bump:** `minor`
**Tag:** `libdd-trace-normalization-v4.1.0`

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)

## libdd-remote-config
**Next version:** `6.0.0`
**Semver bump:** `major`
**Tag:** `libdd-remote-config-v6.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-capabilities-impl`: ^5.0.0 → ^6.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0

### Commits

- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- chore!: remove unused dependencies (v2) (#2511)
- fix(rem-cfg)!: remove AsmRawResponseBody (#2540)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-shared-runtime
**Next version:** `5.0.0`
**Semver bump:** `major`
**Tag:** `libdd-shared-runtime-v5.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-capabilities-impl`: ^5.0.0 → ^6.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0

### Commits

- feat(trace-exporter)!: add API to force flush stats on the trace
exporter (#2538)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-trace-utils
**Next version:** `13.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-utils-v13.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-capabilities-impl`: ^5.0.0 → ^6.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0

### Commits

- fix(trace-utils)!: add forgotten css to agentless v1 encoder (#2557)
- fix(otlp): use potential dedupe in otlp serialization path (#2531)
- feat(trace-utils)!: add v1-native OTLP encoder brick (#2369)
- perf(serialization): bench the actual path used by the trace exporter
(#2512)
- perf(trace): write agentless JSON directly (#2454)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- perf(trace): encode agentless IDs without formatting (#2452)
- perf(trace-utils)!: use pooled spans on the send path (#2382)
- feat(data-pipeline)!: OTLP gRPC trace export (#2171)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)
- fix!: benchmark was doing many samples for deterministic heap usage
(#2465)

## libdd-dogstatsd-client
**Next version:** `7.0.0`
**Semver bump:** `major`
**Tag:** `libdd-dogstatsd-client-v7.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-shared-runtime`: ^4.0.0 → ^5.0.0

### Commits

- chore: move all remaining external deps to workspace-level
dependencies (#2476)

## libdd-telemetry
**Next version:** `9.0.0`
**Semver bump:** `major`
**Tag:** `libdd-telemetry-v9.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-shared-runtime`: ^4.0.0 → ^5.0.0

### Commits

- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- chore!: remove unused dependencies (v2) (#2511)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- fix(telemetry): fall back to the proper intake telemetry domain when
direct submission is enabled (#2484)

## libdd-sampling
**Next version:** `7.0.0`
**Semver bump:** `major`
**Tag:** `libdd-sampling-v7.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^5.2.0 → ^7.0.0
- `libdd-trace-utils`: ^10.1.0 → ^13.0.0

### Commits

- chore(benchmarks): remove batched-loop sampling noise (#2498)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- fix!: benchmark was doing many samples for deterministic heap usage
(#2465)
- feat(trace-utils)!: add from owned to SpanText (#2403)
- test(sampling): make rate_limiter thread-safety test deterministic
(#2354)

## libdd-trace-obfuscation
**Next version:** `9.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-obfuscation-v9.0.0`

### ⚠️ major bump forced due to:

- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-trace-utils`: ^12.0.0 → ^13.0.0

### Commits

- feat(data-pipeline)!: refactor agent's /info obfuscation config format
(#2490)
- fix(obfuscation): keep URLs whose path or fragment holds a bracket
(#2527)
- fix(obfuscation): stop forcing serde_json/preserve_order on dependents
(#2529)
- fix(obfuscation): prevent crash and cap recursion in SQL/HTTP
obfuscation (#2441)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- fix(data-pipeline-ffi): harden agentless config setters and parse
obfuscation config once (#2474)

## libdd-trace-stats
**Next version:** `10.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-stats-v10.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-capabilities-impl`: ^5.0.0 → ^6.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-shared-runtime`: ^4.0.0 → ^5.0.0
- `libdd-trace-obfuscation`: ^8.0.0 → ^9.0.0
- `libdd-trace-utils`: ^12.0.0 → ^13.0.0

### Commits

- feat(trace-exporter)!: add API to force flush stats on the trace
exporter (#2538)
- fix(trace-stats): cardinality limit telemetry name (#2559)
- feat(data-pipeline)!: refactor agent's /info obfuscation config format
(#2490)
- chore!: remove unused dependencies (v2) (#2511)
- feat(data-pipeline)!: generate agentless trace stats (#2488)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)

## libdd-data-pipeline-core
**Next version:** `2.0.0`
**Semver bump:** `major`
**Tag:** `libdd-data-pipeline-core-v2.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-trace-obfuscation`: ^8.0.0 → ^9.0.0
- `libdd-trace-utils`: ^12.0.0 → ^13.0.0

### Commits

- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- feat(data-pipeline)!: generate agentless trace stats (#2488)
- perf(data-pipeline): avoid parsing static entity header names (#2457)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- perf(trace-utils)!: use pooled spans on the send path (#2382)

## libdd-data-pipeline
**Next version:** `11.0.0`
**Semver bump:** `major`
**Tag:** `libdd-data-pipeline-v11.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^3.0.1 → ^4.0.0
- `libdd-capabilities-impl`: ^5.0.0 → ^6.0.0
- `libdd-common`: ^6.0.0 → ^7.0.0
- `libdd-data-pipeline-core`: ^1.0.0 → ^2.0.0
- `libdd-shared-runtime`: ^4.0.0 → ^5.0.0
- `libdd-trace-obfuscation`: ^8.0.0 → ^9.0.0
- `libdd-trace-stats`: ^9.0.0 → ^10.0.0
- `libdd-trace-utils`: ^12.0.0 → ^13.0.0

### Commits

- feat(trace-exporter)!: add API to force flush stats on the trace
exporter (#2538)
- refactor!: apply small timeout pooling strategy to libdd-http-client
as well (#2449)
- feat(data-pipeline)!: refactor agent's /info obfuscation config format
(#2490)
- test(data-pipeline): stop OTLP gRPC post-connect test from hanging
(#2549)
- chore!: remove unused dependencies (v2) (#2511)
- feat(data-pipeline)!: generate agentless trace stats (#2488)
- fix(otlp): use potential dedupe in otlp serialization path (#2531)
- refactor(benchmarks): isolate enqueue timing in data-pipeline (#2499)
- perf(trace): write agentless JSON directly (#2454)
- test(data-pipeline): fix flaky OTLP gRPC exporter integration tests
(#2505)
- chore: move all remaining external deps to workspace-level
dependencies (#2476)
- perf(trace-utils)!: use pooled spans on the send path (#2382)
- feat(data-pipeline)!: OTLP gRPC trace export (#2171)
- chore(libdd-data-pipeline): solve cargo deny [APMSP-3884] (#2318)


[APMSP-3884]:
https://datadoghq.atlassian.net/browse/APMSP-3884?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: paullegranddc <82819397+paullegranddc@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@VianneyRuhlmann VianneyRuhlmann VianneyRuhlmann approved these changes

Assignees

No one assigned

Labels

mergequeue-status: done

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@Eldolfin @VianneyRuhlmann