feat(stats)!: add telemetry for per-field cardinality limits by Eldolfin · Pull Request #2227 · DataDog/libdatadog

Eldolfin · 2026-07-10T15:15:12Z

What does this PR do?

Send telemetry about per-field cardinality collapses. But unlike #2212, now using a single count metric with all the offending fields in the bucket instead of separate count metrics.

Motivation

What inspired you to submit this pull request?

Additional Notes

Anything else we should know when reviewing?

How to test the change?

Describe here in detail how the change can be validated.

datadog-datadog-prod-us1-2 · 2026-07-10T15:17:04Z

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 97.48%
• Overall Coverage: 74.78% (+0.06%)

_{This comment will be updated automatically if new data arrives.

🔗 Commit SHA: 59adf71 | Docs | Datadog PR Page | Give us feedback!}

github-actions · 2026-07-10T15:19:01Z

📚 Documentation Check Results

⚠️ 1857 documentation warning(s) found

📦 `datadog-ipc` - 981 warning(s)

📦 `libdd-trace-stats` - 876 warning(s)

Updated: 2026-07-22 11:19:09 UTC | Commit: 5911d89 | missing-docs job results

github-actions · 2026-07-10T15:19:23Z

🔒 Cargo Deny Results

⚠️ 5 issue(s) found, showing only errors (advisories, bans, sources)

📦 `datadog-ipc` - 3 error(s)

Show output

error[unmaintained]: Bincode is unmaintained
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:25:1
   │
25 │ bincode 1.3.3 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unmaintained advisory detected
   │
   ├ ID: RUSTSEC-2025-0141
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2025-0141
   ├ Due to a doxxing and harassment incident, the bincode team has taken the decision to cease development permanently.
     
     The team considers version 1.3.3 a complete version of bincode that is not in need of any updates.
     
     ## Alternatives to consider
     
     * [wincode](https://crates.io/crates/wincode)
     * [postcard](https://crates.io/crates/postcard)
     * [bitcode](https://crates.io/crates/bitcode)
     * [rkyv](https://crates.io/crates/rkyv)
   ├ Announcement: https://git.sr.ht/~stygianentity/bincode/tree/v3.0/item/README.md
   ├ Solution: No safe upgrade is available!
   ├ bincode v1.3.3
     └── datadog-ipc v0.1.0

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:66:1
   │
66 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── (dev) datadog-ipc v0.1.0
                     ├── libdd-common v5.1.0
                     │   ├── datadog-ipc v0.1.0 (*)
                     │   ├── libdd-capabilities-impl v3.0.0
                     │   │   ├── libdd-shared-runtime v2.0.0
                     │   │   │   └── libdd-trace-stats v6.0.0
                     │   │   │       └── datadog-ipc v0.1.0 (*)
                     │   │   ├── libdd-trace-stats v6.0.0 (*)
                     │   │   └── libdd-trace-utils v9.0.0
                     │   │       ├── libdd-trace-obfuscation v5.0.0
                     │   │       │   └── libdd-trace-stats v6.0.0 (*)
                     │   │       ├── libdd-trace-stats v6.0.0 (*)
                     │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
                     │   ├── libdd-shared-runtime v2.0.0 (*)
                     │   ├── libdd-trace-obfuscation v5.0.0 (*)
                     │   ├── libdd-trace-stats v6.0.0 (*)
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-ddsketch v1.1.0
                     │   ├── datadog-ipc v0.1.0 (*)
                     │   └── libdd-trace-stats v6.0.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.0
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-trace-obfuscation v5.0.0 (*)
                     ├── (dev) libdd-trace-stats v6.0.0 (*)
                     └── (dev) libdd-trace-utils v9.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:205:1
    │
205 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v5.1.0
      │   ├── datadog-ipc v0.1.0
      │   ├── libdd-capabilities-impl v3.0.0
      │   │   ├── libdd-shared-runtime v2.0.0
      │   │   │   └── libdd-trace-stats v6.0.0
      │   │   │       └── datadog-ipc v0.1.0 (*)
      │   │   ├── libdd-trace-stats v6.0.0 (*)
      │   │   └── libdd-trace-utils v9.0.0
      │   │       ├── libdd-trace-obfuscation v5.0.0
      │   │       │   └── libdd-trace-stats v6.0.0 (*)
      │   │       ├── libdd-trace-stats v6.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
      │   ├── libdd-shared-runtime v2.0.0 (*)
      │   ├── libdd-trace-obfuscation v5.0.0 (*)
      │   ├── libdd-trace-stats v6.0.0 (*)
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-ddsketch v1.1.0
      │   ├── datadog-ipc v0.1.0 (*)
      │   └── libdd-trace-stats v6.0.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.0
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-trace-stats v6.0.0 (*)
      ├── libdd-trace-utils v9.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── datadog-ipc v0.1.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v9.0.0 (*)

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-stats` - 2 error(s)

Show output

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:66:1
   │
66 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── libdd-common v5.1.0
                     │   ├── libdd-capabilities-impl v3.0.0
                     │   │   ├── libdd-shared-runtime v2.0.0
                     │   │   │   ├── libdd-telemetry v6.0.0
                     │   │   │   │   └── libdd-trace-stats v6.0.0
                     │   │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   │   ├── (dev) libdd-telemetry v6.0.0 (*)
                     │   │   ├── libdd-trace-stats v6.0.0 (*)
                     │   │   └── libdd-trace-utils v9.0.0
                     │   │       ├── libdd-trace-obfuscation v5.0.0
                     │   │       │   └── libdd-trace-stats v6.0.0 (*)
                     │   │       ├── libdd-trace-stats v6.0.0 (*)
                     │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
                     │   ├── libdd-dogstatsd-client v4.0.0
                     │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   ├── libdd-shared-runtime v2.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   ├── libdd-trace-obfuscation v5.0.0 (*)
                     │   ├── libdd-trace-stats v6.0.0 (*)
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-ddsketch v1.1.0
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   └── libdd-trace-stats v6.0.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.0
                     │   └── libdd-trace-utils v9.0.0 (*)
                     ├── (dev) libdd-trace-obfuscation v5.0.0 (*)
                     ├── (dev) libdd-trace-stats v6.0.0 (*)
                     └── (dev) libdd-trace-utils v9.0.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:198:1
    │
198 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── libdd-common v5.1.0
      │   ├── libdd-capabilities-impl v3.0.0
      │   │   ├── libdd-shared-runtime v2.0.0
      │   │   │   ├── libdd-telemetry v6.0.0
      │   │   │   │   └── libdd-trace-stats v6.0.0
      │   │   │   └── libdd-trace-stats v6.0.0 (*)
      │   │   ├── (dev) libdd-telemetry v6.0.0 (*)
      │   │   ├── libdd-trace-stats v6.0.0 (*)
      │   │   └── libdd-trace-utils v9.0.0
      │   │       ├── libdd-trace-obfuscation v5.0.0
      │   │       │   └── libdd-trace-stats v6.0.0 (*)
      │   │       ├── libdd-trace-stats v6.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v9.0.0 (*)
      │   ├── libdd-dogstatsd-client v4.0.0
      │   │   └── libdd-trace-stats v6.0.0 (*)
      │   ├── libdd-shared-runtime v2.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   ├── libdd-trace-obfuscation v5.0.0 (*)
      │   ├── libdd-trace-stats v6.0.0 (*)
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-ddsketch v1.1.0
      │   ├── libdd-telemetry v6.0.0 (*)
      │   └── libdd-trace-stats v6.0.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.0
      │   └── libdd-trace-utils v9.0.0 (*)
      ├── (dev) libdd-trace-stats v6.0.0 (*)
      ├── libdd-trace-utils v9.0.0 (*)
      └── proptest v1.5.0
          └── (dev) libdd-tinybytes v1.1.1
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v9.0.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-07-22 11:20:20 UTC | Commit: 5911d89 | dependency-check job results

pr-commenter · 2026-07-21T12:15:22Z

Benchmarks

Comparison

Benchmark execution time: 2026-07-22 11:28:34

Comparing candidate commit 59adf71 in PR branch oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator with baseline commit 85c73e9 in branch oscarld/stats-per-key-cardinality-limit.

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-07-22 11:25:16

Comparing candidate commit 59adf71 in PR branch oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator with baseline commit 85c73e9 in branch oscarld/stats-per-key-cardinality-limit.

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 8259CL CPU @ 2.50GHz	`59adf71`	1784719014	oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator

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	56.332ms	56.594ms ± 0.169ms	56.546ms ± 0.072ms	56.659ms	56.921ms	57.153ms	57.383ms	1.48%	1.485	3.113	0.30%	0.012ms	1	200
trace_buffer/1_senders/10us_delay	throughput	15683.969op/s	15902.788op/s ± 47.405op/s	15916.215op/s ± 20.317op/s	15934.103op/s	15959.680op/s	15971.802op/s	15976.605op/s	0.38%	-1.459	3.001	0.30%	3.352op/s	1	200
trace_buffer/1_senders/1us_delay	execution_time	49.976ms	50.078ms ± 0.027ms	50.076ms ± 0.010ms	50.086ms	50.135ms	50.184ms	50.197ms	0.24%	1.302	5.206	0.05%	0.002ms	1	200
trace_buffer/1_senders/1us_delay	throughput	17929.488op/s	17971.806op/s ± 9.652op/s	17972.691op/s ± 3.534op/s	17976.539op/s	17983.479op/s	17991.518op/s	18008.482op/s	0.20%	-1.293	5.190	0.05%	0.683op/s	1	200
trace_buffer/1_senders/no_delay	execution_time	331.571µs	338.100µs ± 4.953µs	337.278µs ± 1.621µs	339.217µs	342.517µs	351.945µs	392.037µs	16.24%	6.900	69.424	1.46%	0.350µs	1	200
trace_buffer/1_senders/no_delay	throughput	2295703.033op/s	2662449.550op/s ± 35667.682op/s	2668424.542op/s ± 12776.354op/s	2678880.241op/s	2697285.014op/s	2710214.130op/s	2714349.303op/s	1.72%	-5.939	55.259	1.34%	2522.086op/s	1	200
trace_buffer/2_senders/10us_delay	execution_time	56.818ms	57.280ms ± 0.196ms	57.286ms ± 0.120ms	57.399ms	57.496ms	57.551ms	59.091ms	3.15%	3.742	34.768	0.34%	0.014ms	1	200
trace_buffer/2_senders/10us_delay	throughput	30461.500op/s	31424.855op/s ± 106.193op/s	31421.550op/s ± 65.652op/s	31488.779op/s	31566.530op/s	31630.136op/s	31680.269op/s	0.82%	-3.515	32.207	0.34%	7.509op/s	1	200
trace_buffer/2_senders/1us_delay	execution_time	50.059ms	50.107ms ± 0.031ms	50.103ms ± 0.017ms	50.120ms	50.162ms	50.193ms	50.268ms	0.33%	1.456	3.934	0.06%	0.002ms	1	200
trace_buffer/2_senders/1us_delay	throughput	35808.236op/s	35923.430op/s ± 21.905op/s	35926.224op/s ± 12.538op/s	35938.917op/s	35950.051op/s	35955.228op/s	35957.549op/s	0.09%	-1.449	3.895	0.06%	1.549op/s	1	200
trace_buffer/2_senders/no_delay	execution_time	829.550µs	879.276µs ± 18.865µs	881.152µs ± 13.997µs	893.393µs	905.892µs	916.952µs	937.733µs	6.42%	0.013	-0.326	2.14%	1.334µs	1	200
trace_buffer/2_senders/no_delay	throughput	1919522.073op/s	2048077.547op/s ± 43979.937op/s	2042780.125op/s ± 32050.511op/s	2080899.732op/s	2122076.763op/s	2138194.179op/s	2169850.436op/s	6.22%	0.093	-0.360	2.14%	3109.851op/s	1	200
trace_buffer/4_senders/10us_delay	execution_time	57.361ms	57.599ms ± 0.167ms	57.575ms ± 0.055ms	57.636ms	57.758ms	57.972ms	59.499ms	3.34%	7.530	81.685	0.29%	0.012ms	1	200
trace_buffer/4_senders/10us_delay	throughput	60505.369op/s	62501.523op/s ± 177.660op/s	62527.263op/s ± 60.189op/s	62576.230op/s	62661.537op/s	62706.091op/s	62760.345op/s	0.37%	-7.299	78.122	0.28%	12.562op/s	1	200
trace_buffer/4_senders/1us_delay	execution_time	50.088ms	50.177ms ± 0.036ms	50.170ms ± 0.024ms	50.199ms	50.239ms	50.293ms	50.340ms	0.34%	1.085	2.122	0.07%	0.003ms	1	200
trace_buffer/4_senders/1us_delay	throughput	71513.995op/s	71745.503op/s ± 51.974op/s	71756.067op/s ± 34.473op/s	71780.035op/s	71812.071op/s	71823.519op/s	71873.094op/s	0.16%	-1.078	2.098	0.07%	3.675op/s	1	200
trace_buffer/4_senders/no_delay	execution_time	2.227ms	2.430ms ± 0.075ms	2.436ms ± 0.050ms	2.485ms	2.540ms	2.578ms	2.605ms	6.94%	-0.309	-0.140	3.06%	0.005ms	1	200
trace_buffer/4_senders/no_delay	throughput	1382118.080op/s	1482828.403op/s ± 46024.601op/s	1478091.419op/s ± 29706.362op/s	1510715.817op/s	1572442.394op/s	1595182.810op/s	1616856.784op/s	9.39%	0.474	0.028	3.10%	3254.431op/s	1	200
trace_buffer/8_senders/10us_delay	execution_time	57.725ms	58.022ms ± 0.237ms	57.937ms ± 0.126ms	58.178ms	58.499ms	58.633ms	58.646ms	1.22%	0.957	-0.136	0.41%	0.017ms	1	200
trace_buffer/8_senders/10us_delay	throughput	122771.545op/s	124093.867op/s ± 503.994op/s	124272.913op/s ± 270.829op/s	124508.489op/s	124630.771op/s	124694.680op/s	124730.163op/s	0.37%	-0.946	-0.163	0.41%	35.638op/s	1	200
trace_buffer/8_senders/1us_delay	execution_time	50.195ms	50.283ms ± 0.060ms	50.268ms ± 0.028ms	50.305ms	50.385ms	50.502ms	50.633ms	0.73%	2.340	8.295	0.12%	0.004ms	1	200
trace_buffer/8_senders/1us_delay	throughput	142199.007op/s	143191.140op/s ± 170.072op/s	143233.594op/s ± 78.539op/s	143294.616op/s	143363.157op/s	143412.551op/s	143439.416op/s	0.14%	-2.323	8.178	0.12%	12.026op/s	1	200
trace_buffer/8_senders/no_delay	execution_time	5.920ms	6.424ms ± 0.089ms	6.446ms ± 0.041ms	6.478ms	6.523ms	6.570ms	6.575ms	1.99%	-1.719	5.294	1.39%	0.006ms	1	200
trace_buffer/8_senders/no_delay	throughput	1095056.979op/s	1121067.741op/s ± 16011.014op/s	1116893.830op/s ± 7063.458op/s	1126225.380op/s	1152375.701op/s	1170946.630op/s	1216316.891op/s	8.90%	1.913	6.540	1.42%	1132.150op/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	[56.571ms; 56.618ms] or [-0.041%; +0.041%]	None	None	None
trace_buffer/1_senders/10us_delay	throughput	[15896.219op/s; 15909.358op/s] or [-0.041%; +0.041%]	None	None	None
trace_buffer/1_senders/1us_delay	execution_time	[50.075ms; 50.082ms] or [-0.007%; +0.007%]	None	None	None
trace_buffer/1_senders/1us_delay	throughput	[17970.469op/s; 17973.144op/s] or [-0.007%; +0.007%]	None	None	None
trace_buffer/1_senders/no_delay	execution_time	[337.414µs; 338.787µs] or [-0.203%; +0.203%]	None	None	None
trace_buffer/1_senders/no_delay	throughput	[2657506.353op/s; 2667392.748op/s] or [-0.186%; +0.186%]	None	None	None
trace_buffer/2_senders/10us_delay	execution_time	[57.253ms; 57.307ms] or [-0.047%; +0.047%]	None	None	None
trace_buffer/2_senders/10us_delay	throughput	[31410.137op/s; 31439.572op/s] or [-0.047%; +0.047%]	None	None	None
trace_buffer/2_senders/1us_delay	execution_time	[50.102ms; 50.111ms] or [-0.008%; +0.008%]	None	None	None
trace_buffer/2_senders/1us_delay	throughput	[35920.394op/s; 35926.466op/s] or [-0.008%; +0.008%]	None	None	None
trace_buffer/2_senders/no_delay	execution_time	[876.661µs; 881.890µs] or [-0.297%; +0.297%]	None	None	None
trace_buffer/2_senders/no_delay	throughput	[2041982.351op/s; 2054172.743op/s] or [-0.298%; +0.298%]	None	None	None
trace_buffer/4_senders/10us_delay	execution_time	[57.576ms; 57.622ms] or [-0.040%; +0.040%]	None	None	None
trace_buffer/4_senders/10us_delay	throughput	[62476.901op/s; 62526.145op/s] or [-0.039%; +0.039%]	None	None	None
trace_buffer/4_senders/1us_delay	execution_time	[50.172ms; 50.182ms] or [-0.010%; +0.010%]	None	None	None
trace_buffer/4_senders/1us_delay	throughput	[71738.300op/s; 71752.706op/s] or [-0.010%; +0.010%]	None	None	None
trace_buffer/4_senders/no_delay	execution_time	[2.420ms; 2.440ms] or [-0.425%; +0.425%]	None	None	None
trace_buffer/4_senders/no_delay	throughput	[1476449.836op/s; 1489206.970op/s] or [-0.430%; +0.430%]	None	None	None
trace_buffer/8_senders/10us_delay	execution_time	[57.989ms; 58.054ms] or [-0.057%; +0.057%]	None	None	None
trace_buffer/8_senders/10us_delay	throughput	[124024.018op/s; 124163.716op/s] or [-0.056%; +0.056%]	None	None	None
trace_buffer/8_senders/1us_delay	execution_time	[50.274ms; 50.291ms] or [-0.017%; +0.017%]	None	None	None
trace_buffer/8_senders/1us_delay	throughput	[143167.570op/s; 143214.710op/s] or [-0.016%; +0.016%]	None	None	None
trace_buffer/8_senders/no_delay	execution_time	[6.411ms; 6.436ms] or [-0.193%; +0.193%]	None	None	None
trace_buffer/8_senders/no_delay	throughput	[1118848.769op/s; 1123286.714op/s] or [-0.198%; +0.198%]	None	None	None

Group 1

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`59adf71`	1784719014	oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator

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.550µs	15.845µs ± 0.139µs	15.829µs ± 0.073µs	15.912µs	16.064µs	16.286µs	16.416µs	3.71%	0.873	1.977	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	[15.826µs; 15.864µs] or [-0.121%; +0.121%]	None	None	None

Group 2

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`59adf71`	1784719014	oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator

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.606ms	9.631ms ± 0.016ms	9.629ms ± 0.011ms	9.641ms	9.660ms	9.671ms	9.685ms	0.59%	0.737	0.222	0.16%	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.629ms; 9.633ms] or [-0.022%; +0.022%]	None	None	None

Group 3

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`59adf71`	1784719014	oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator

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.051µs	1.071µs ± 0.007µs	1.071µs ± 0.005µs	1.077µs	1.082µs	1.084µs	1.085µs	1.37%	-0.132	-0.685	0.65%	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.070µs; 1.072µs] or [-0.091%; +0.091%]	None	None	None

Baseline

Baseline benchmark details

Group 1

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`85c73e9`	1784718237	oscarld/stats-per-key-cardinality-limit

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	56.289ms	56.693ms ± 0.350ms	56.532ms ± 0.107ms	56.820ms	57.489ms	57.597ms	57.733ms	2.12%	1.315	0.514	0.62%	0.025ms	1	200
trace_buffer/1_senders/10us_delay	throughput	15589.008op/s	15875.443op/s ± 97.207op/s	15920.214op/s ± 30.004op/s	15939.312op/s	15962.091op/s	15973.681op/s	15988.963op/s	0.43%	-1.300	0.471	0.61%	6.874op/s	1	200
trace_buffer/1_senders/1us_delay	execution_time	49.977ms	50.078ms ± 0.030ms	50.079ms ± 0.009ms	50.085ms	50.138ms	50.185ms	50.192ms	0.22%	0.900	3.305	0.06%	0.002ms	1	200
trace_buffer/1_senders/1us_delay	throughput	17931.260op/s	17971.845op/s ± 10.903op/s	17971.572op/s ± 3.108op/s	17975.939op/s	17989.906op/s	17992.124op/s	18008.166op/s	0.20%	-0.892	3.292	0.06%	0.771op/s	1	200
trace_buffer/1_senders/no_delay	execution_time	328.208µs	337.234µs ± 5.435µs	336.530µs ± 1.461µs	338.134µs	342.295µs	349.911µs	399.584µs	18.74%	7.773	85.129	1.61%	0.384µs	1	200
trace_buffer/1_senders/no_delay	throughput	2252342.147op/s	2669385.861op/s ± 38583.658op/s	2674355.315op/s ± 11661.385op/s	2685768.269op/s	2702349.276op/s	2725667.260op/s	2742166.934op/s	2.54%	-6.571	66.904	1.44%	2728.277op/s	1	200
trace_buffer/2_senders/10us_delay	execution_time	56.484ms	56.868ms ± 0.190ms	56.834ms ± 0.111ms	56.960ms	57.244ms	57.362ms	57.742ms	1.60%	1.249	2.619	0.33%	0.013ms	1	200
trace_buffer/2_senders/10us_delay	throughput	31172.922op/s	31652.645op/s ± 105.233op/s	31671.179op/s ± 61.650op/s	31719.803op/s	31786.893op/s	31822.594op/s	31867.202op/s	0.62%	-1.219	2.492	0.33%	7.441op/s	1	200
trace_buffer/2_senders/1us_delay	execution_time	50.055ms	50.112ms ± 0.035ms	50.108ms ± 0.016ms	50.122ms	50.193ms	50.237ms	50.279ms	0.34%	1.878	4.534	0.07%	0.003ms	1	200
trace_buffer/2_senders/1us_delay	throughput	35800.542op/s	35919.530op/s ± 25.407op/s	35922.708op/s ± 11.614op/s	35935.926op/s	35947.627op/s	35954.958op/s	35960.724op/s	0.11%	-1.872	4.505	0.07%	1.797op/s	1	200
trace_buffer/2_senders/no_delay	execution_time	847.989µs	900.105µs ± 17.544µs	902.238µs ± 11.386µs	912.729µs	925.098µs	930.923µs	933.647µs	3.48%	-0.691	0.291	1.94%	1.241µs	1	200
trace_buffer/2_senders/no_delay	throughput	1927923.050op/s	2000534.756op/s ± 39565.913op/s	1995039.802op/s ± 24863.734op/s	2022783.668op/s	2081400.680op/s	2116230.740op/s	2122670.018op/s	6.40%	0.799	0.493	1.97%	2797.733op/s	1	200
trace_buffer/4_senders/10us_delay	execution_time	57.095ms	57.438ms ± 0.148ms	57.434ms ± 0.110ms	57.544ms	57.675ms	57.827ms	57.936ms	0.87%	0.501	0.086	0.26%	0.010ms	1	200
trace_buffer/4_senders/10us_delay	throughput	62137.572op/s	62676.380op/s ± 160.849op/s	62680.410op/s ± 119.511op/s	62804.844op/s	62902.390op/s	62976.223op/s	63053.198op/s	0.59%	-0.487	0.061	0.26%	11.374op/s	1	200
trace_buffer/4_senders/1us_delay	execution_time	50.083ms	50.173ms ± 0.044ms	50.162ms ± 0.019ms	50.185ms	50.268ms	50.298ms	50.312ms	0.30%	1.155	0.784	0.09%	0.003ms	1	200
trace_buffer/4_senders/1us_delay	throughput	71553.742op/s	71752.050op/s ± 62.647op/s	71768.168op/s ± 27.162op/s	71792.388op/s	71827.538op/s	71838.600op/s	71880.908op/s	0.16%	-1.152	0.776	0.09%	4.430op/s	1	200
trace_buffer/4_senders/no_delay	execution_time	2.321ms	2.441ms ± 0.042ms	2.444ms ± 0.027ms	2.469ms	2.508ms	2.534ms	2.550ms	4.34%	-0.233	0.066	1.72%	0.003ms	1	200
trace_buffer/4_senders/no_delay	throughput	1411815.721op/s	1474988.231op/s ± 25610.274op/s	1473021.395op/s ± 16104.718op/s	1489854.887op/s	1522401.597op/s	1534383.388op/s	1550785.550op/s	5.28%	0.337	0.118	1.73%	1810.920op/s	1	200
trace_buffer/8_senders/10us_delay	execution_time	57.632ms	57.932ms ± 0.202ms	57.884ms ± 0.118ms	58.033ms	58.333ms	58.483ms	58.494ms	1.05%	0.957	0.123	0.35%	0.014ms	1	200
trace_buffer/8_senders/10us_delay	throughput	123089.127op/s	124285.094op/s ± 432.696op/s	124385.812op/s ± 253.642op/s	124621.121op/s	124781.355op/s	124891.598op/s	124930.774op/s	0.44%	-0.944	0.094	0.35%	30.596op/s	1	200
trace_buffer/8_senders/1us_delay	execution_time	50.202ms	50.279ms ± 0.053ms	50.267ms ± 0.026ms	50.303ms	50.381ms	50.442ms	50.493ms	0.45%	1.438	2.308	0.10%	0.004ms	1	200
trace_buffer/8_senders/1us_delay	throughput	142593.729op/s	143200.142op/s ± 149.363op/s	143235.129op/s ± 73.627op/s	143297.384op/s	143365.903op/s	143411.996op/s	143420.287op/s	0.13%	-1.431	2.281	0.10%	10.562op/s	1	200
trace_buffer/8_senders/no_delay	execution_time	5.484ms	6.385ms ± 0.212ms	6.434ms ± 0.109ms	6.534ms	6.609ms	6.638ms	6.677ms	3.79%	-1.660	3.254	3.32%	0.015ms	1	200
trace_buffer/8_senders/no_delay	throughput	1078275.137op/s	1129009.361op/s ± 39918.926op/s	1119116.154op/s ± 18996.492op/s	1140107.953op/s	1218003.520op/s	1263005.677op/s	1312988.416op/s	17.32%	1.934	4.603	3.53%	2822.694op/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	[56.645ms; 56.742ms] or [-0.086%; +0.086%]	None	None	None
trace_buffer/1_senders/10us_delay	throughput	[15861.971op/s; 15888.915op/s] or [-0.085%; +0.085%]	None	None	None
trace_buffer/1_senders/1us_delay	execution_time	[50.074ms; 50.083ms] or [-0.008%; +0.008%]	None	None	None
trace_buffer/1_senders/1us_delay	throughput	[17970.334op/s; 17973.356op/s] or [-0.008%; +0.008%]	None	None	None
trace_buffer/1_senders/no_delay	execution_time	[336.481µs; 337.987µs] or [-0.223%; +0.223%]	None	None	None
trace_buffer/1_senders/no_delay	throughput	[2664038.537op/s; 2674733.184op/s] or [-0.200%; +0.200%]	None	None	None
trace_buffer/2_senders/10us_delay	execution_time	[56.842ms; 56.894ms] or [-0.046%; +0.046%]	None	None	None
trace_buffer/2_senders/10us_delay	throughput	[31638.061op/s; 31667.229op/s] or [-0.046%; +0.046%]	None	None	None
trace_buffer/2_senders/1us_delay	execution_time	[50.107ms; 50.117ms] or [-0.010%; +0.010%]	None	None	None
trace_buffer/2_senders/1us_delay	throughput	[35916.009op/s; 35923.052op/s] or [-0.010%; +0.010%]	None	None	None
trace_buffer/2_senders/no_delay	execution_time	[897.673µs; 902.536µs] or [-0.270%; +0.270%]	None	None	None
trace_buffer/2_senders/no_delay	throughput	[1995051.301op/s; 2006018.211op/s] or [-0.274%; +0.274%]	None	None	None
trace_buffer/4_senders/10us_delay	execution_time	[57.418ms; 57.459ms] or [-0.036%; +0.036%]	None	None	None
trace_buffer/4_senders/10us_delay	throughput	[62654.088op/s; 62698.672op/s] or [-0.036%; +0.036%]	None	None	None
trace_buffer/4_senders/1us_delay	execution_time	[50.167ms; 50.179ms] or [-0.012%; +0.012%]	None	None	None
trace_buffer/4_senders/1us_delay	throughput	[71743.368op/s; 71760.733op/s] or [-0.012%; +0.012%]	None	None	None
trace_buffer/4_senders/no_delay	execution_time	[2.436ms; 2.447ms] or [-0.239%; +0.239%]	None	None	None
trace_buffer/4_senders/no_delay	throughput	[1471438.893op/s; 1478537.568op/s] or [-0.241%; +0.241%]	None	None	None
trace_buffer/8_senders/10us_delay	execution_time	[57.904ms; 57.960ms] or [-0.048%; +0.048%]	None	None	None
trace_buffer/8_senders/10us_delay	throughput	[124225.126op/s; 124345.061op/s] or [-0.048%; +0.048%]	None	None	None
trace_buffer/8_senders/1us_delay	execution_time	[50.272ms; 50.287ms] or [-0.014%; +0.014%]	None	None	None
trace_buffer/8_senders/1us_delay	throughput	[143179.442op/s; 143220.842op/s] or [-0.014%; +0.014%]	None	None	None
trace_buffer/8_senders/no_delay	execution_time	[6.355ms; 6.414ms] or [-0.461%; +0.461%]	None	None	None
trace_buffer/8_senders/no_delay	throughput	[1123476.982op/s; 1134541.741op/s] or [-0.490%; +0.490%]	None	None	None

Group 1

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`85c73e9`	1784718237	oscarld/stats-per-key-cardinality-limit

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.196µs	15.522µs ± 0.154µs	15.486µs ± 0.088µs	15.601µs	15.791µs	15.949µs	16.298µs	5.25%	1.207	3.185	0.99%	0.011µ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.500µs; 15.543µs] or [-0.138%; +0.138%]	None	None	None

Group 2

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`85c73e9`	1784718237	oscarld/stats-per-key-cardinality-limit

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.590ms	9.616ms ± 0.016ms	9.611ms ± 0.010ms	9.625ms	9.647ms	9.670ms	9.673ms	0.64%	1.109	1.193	0.17%	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.613ms; 9.618ms] or [-0.023%; +0.023%]	None	None	None

Group 3

cpu_model	git_commit_sha	git_commit_date	git_branch
Intel(R) Xeon(R) Platinum 8259CL CPU @ 2.50GHz	`85c73e9`	1784718237	oscarld/stats-per-key-cardinality-limit

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.052µs	1.068µs ± 0.006µs	1.069µs ± 0.003µs	1.071µs	1.078µs	1.087µs	1.094µs	2.34%	0.333	1.584	0.59%	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.068µs; 1.069µs] or [-0.082%; +0.082%]	None	None	None

Eldolfin · 2026-07-21T12:24:22Z

@codex review

dd-octo-sts · 2026-07-21T12:37:21Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	88.18 MB	88.30 MB	+.14% (+132.77 KB) 🔍
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.13 MB	8.13 MB	+0% (+48 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	10.93 MB	10.94 MB	+.03% (+4.30 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	99.46 MB	99.59 MB	+.13% (+136.37 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.59 MB	26.62 MB	+.11% (+30.00 KB) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	89.18 KB	89.60 KB	+.47% (+430 B) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	191.30 MB	191.47 MB	+.08% (+176.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	1.04 GB	1.04 GB	+0% (+78.31 KB) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.66 MB	8.67 MB	+.13% (+12.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	89.18 KB	89.60 KB	+.47% (+430 B) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.36 MB	25.39 MB	+.12% (+32.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	50.55 MB	50.62 MB	+.13% (+69.74 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.16 MB	23.19 MB	+.12% (+30.50 KB) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	90.58 KB	91.00 KB	+.46% (+434 B) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	195.94 MB	196.17 MB	+.11% (+232.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	1.03 GB	1.03 GB	+.19% (+2.07 MB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.68 MB	6.69 MB	+.18% (+13.00 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	90.58 KB	91.00 KB	+.46% (+434 B) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.26 MB	27.31 MB	+.17% (+48.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.13 MB	48.19 MB	+.13% (+68.29 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	78.64 MB	78.76 MB	+.14% (+119.10 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.05 MB	9.07 MB	+.21% (+20.06 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	94.14 MB	94.26 MB	+.13% (+125.67 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.02 MB	11.03 MB	+.16% (+19.14 KB) 🔍

chatgpt-codex-connector · 2026-07-21T12:37:36Z

Codex Review: Didn't find any major issues. Keep them coming!

Reviewed commit: e1430135ee

ℹ️ 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

datadog-datadog-prod-us1-2 · 2026-07-21T14:24:23Z

Bits has a CI fix ready

🟢 Investigated · 🟢 Fix prepared · ⚪ Validation skipped · 🟠 Ready

test_collapsed_spans_telemetry dropped its HTTP mock before StatsExporter::send completed. The test now retains the mock for its full lifetime in libdd-trace-stats/src/stats_exporter.rs.

Commit fix to this PR

View in Datadog | Reviewed commit e47093e · Any feedback? Reach out in #deveng-pr-agent

feat: doc new module

Eldolfin · 2026-07-22T11:17:10Z

@copilot review

github-actions Bot added sidecar data-pipeline labels Jul 10, 2026

Eldolfin changed the base branch from main to oscarld/stats-per-key-cardinality-limit July 10, 2026 15:15

github-actions Bot removed sidecar data-pipeline labels Jul 10, 2026

Eldolfin mentioned this pull request Jul 21, 2026

feat(stats)!: add telemetry for per-field cardinality limits #2212

Closed

Eldolfin force-pushed the oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator branch from 456c9bf to 295db59 Compare July 21, 2026 12:01

Eldolfin changed the title ~~feat(stats)!: add telemetry for per-field cardinality limits V2~~ feat(stats)!: add telemetry for per-field cardinality limits Jul 21, 2026

Eldolfin force-pushed the oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator branch from e47093e to cd350fa Compare July 22, 2026 11:00

Eldolfin added 9 commits July 22, 2026 13:05

feat: fields combination metrics, dogstatsd only

1d6f370

feat: cherry pick simple 1 collapsed field tests from old pr

d9740e2

fix: bitshift operations are hard...

171683e

cleanup

6ff1899

wip telemetry

0571862

add tests for multiple per-key collapse

4205724

refacto: extract telemetry stuff into its own module

7820438

feat: doc new module

fix: assert -> debug_assert, avoid useless unreachable!

76d3c4b

feat: telemetry for additional metric tags collapse

e648bf3

Eldolfin force-pushed the oscarld/stats-per-key-cardinality-limit-telemetry-in-concentrator branch from bf05f1a to e648bf3 Compare July 22, 2026 11:05

remove old fixme

59adf71

Eldolfin marked this pull request as ready for review July 22, 2026 11:17

Eldolfin requested review from a team as code owners July 22, 2026 11:17

Uh oh!

Conversation

Eldolfin commented Jul 10, 2026

What does this PR do?

Motivation

Additional Notes

How to test the change?

Uh oh!

datadog-datadog-prod-us1-2 Bot commented Jul 10, 2026 • edited by datadog-prod-us1-5 Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

github-actions Bot commented Jul 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Documentation Check Results

📦 datadog-ipc - 981 warning(s)

📦 libdd-trace-stats - 876 warning(s)

Uh oh!

github-actions Bot commented Jul 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Cargo Deny Results

📦 datadog-ipc - 3 error(s)

📦 libdd-trace-stats - 2 error(s)

Uh oh!

pr-commenter Bot commented Jul 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Comparison

Explanation

More details about the CI and significant changes

Explanation

More details about the CI and significant changes

Candidate

Group 1

Group 1

Group 2

Group 3

Baseline

Group 1

Group 1

Group 2

Group 3

Uh oh!

Eldolfin commented Jul 21, 2026

Uh oh!

dd-octo-sts Bot commented Jul 21, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Artifact Size Benchmark Report

Uh oh!

chatgpt-codex-connector Bot commented Jul 21, 2026

Uh oh!

datadog-datadog-prod-us1-2 Bot commented Jul 21, 2026 • edited by datadog-datadog-prod-us1 Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Bits has a CI fix ready

Uh oh!

Eldolfin commented Jul 22, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

datadog-datadog-prod-us1-2 Bot commented Jul 10, 2026 •

edited by datadog-prod-us1-5 Bot

Loading

github-actions Bot commented Jul 10, 2026 •

edited

Loading

📦 `datadog-ipc` - 981 warning(s)

📦 `libdd-trace-stats` - 876 warning(s)

github-actions Bot commented Jul 10, 2026 •

edited

Loading

📦 `datadog-ipc` - 3 error(s)

📦 `libdd-trace-stats` - 2 error(s)

pr-commenter Bot commented Jul 21, 2026 •

edited

Loading

dd-octo-sts Bot commented Jul 21, 2026 •

edited

Loading

datadog-datadog-prod-us1-2 Bot commented Jul 21, 2026 •

edited by datadog-datadog-prod-us1 Bot

Loading