feat(data-pipeline): emit native trace export telemetry by mabdinur · Pull Request #2338 · DataDog/libdatadog

mabdinur · 2026-08-10T19:07:42Z

Summary

Follow-up to DataDog/dd-trace-py#18967, which adds trace-writer telemetry to the Python writer.

When dd-trace-py uses NativeWriter, libdatadog owns trace serialization and export. This PR emits the same telemetry from the native writer so metrics remain consistent across writer implementations.

It covers every native trace export path:

Agentless JSON
Agent v0.4 msgpack
Agent v0.5 msgpack
Agent v1 msgpack
OTLP

Metrics

Records spans_enqueued_for_serialization before export.
Records spans_dropped for definitive serialization and API failures.
Records trace_api requests, responses, errors, bytes, and chunks for agentless and OTLP, matching the existing agent export behavior.

Implementation notes

The exporter observes the raw retry result before mapping it to the existing TraceExporterError. Agentless export reuses the telemetry worker supplied by dd-trace-py. Existing transport function visibility and re-exports are preserved; the transport modules remain crate-internal.

Test plan

cargo check -p libdd-data-pipeline
cargo check -p libdd-data-pipeline --no-default-features
cargo nextest run -p libdd-data-pipeline (173 passed)
cargo +stable clippy -p libdd-data-pipeline --all-targets -- -D warnings
cargo +nightly-2026-07-26 fmt --all -- --check
cargo bench -p libdd-data-pipeline --bench trace_buffer -- --quick

github-actions · 2026-08-10T19:09:32Z

📚 Documentation Check Results

⚠️ 1278 documentation warning(s) found

📦 `libdd-data-pipeline` - 1278 warning(s)

Updated: 2026-08-10 20:58:41 UTC | Commit: 4f0edce | missing-docs job results

github-actions · 2026-08-10T19:12:04Z

🔒 Cargo Deny Results

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

📦 `libdd-data-pipeline` - 3 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:77:1
   │
77 │ 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-data-pipeline v7.0.0
                     │   │   ├── libdd-shared-runtime v2.0.0
                     │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   ├── libdd-dogstatsd-client v4.0.0
                     │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   │   └── libdd-trace-stats v6.0.0
                     │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   ├── libdd-telemetry v6.0.0
                     │   │   │   │   ├── libdd-data-pipeline v7.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-data-pipeline v7.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-data-pipeline v7.0.0 (*)
                     │   ├── libdd-dogstatsd-client v4.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-data-pipeline v7.0.0 (*)
                     ├── (dev) libdd-ddsketch v1.1.0
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   └── libdd-trace-stats v6.0.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.0
                     │   ├── libdd-data-pipeline v7.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:223:1
    │
223 │ 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-data-pipeline v7.0.0
      │   │   ├── libdd-shared-runtime v2.0.0
      │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   ├── libdd-dogstatsd-client v4.0.0
      │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v6.0.0
      │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
      │   │   │   ├── libdd-telemetry v6.0.0
      │   │   │   │   ├── libdd-data-pipeline v7.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-data-pipeline v7.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-data-pipeline v7.0.0 (*)
      │   ├── libdd-dogstatsd-client v4.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-data-pipeline v7.0.0 (*)
      ├── (dev) libdd-ddsketch v1.1.0
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   └── libdd-trace-stats v6.0.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.0
      │   ├── libdd-data-pipeline v7.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-common v5.1.0 (*)
          └── (dev) libdd-tinybytes v1.1.1
              ├── libdd-data-pipeline v7.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.1 (*)
              └── libdd-trace-utils v9.0.0 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:295:1
    │
295 │ time 0.3.41 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0009
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0009
    ├ ## Impact
      
      When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of
      service attack via stack exhaustion is possible. The attack relies on formally deprecated and
      rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary,
      non-malicious input will never encounter this scenario.
      
      ## Patches
      
      A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned
      rather than exhausting the stack.
      
      ## Workarounds
      
      Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of
      the stack consumed would be at most a factor of the length of the input.
    ├ Announcement: https://github.com/time-rs/time/blob/main/CHANGELOG.md#0347-2026-02-05
    ├ Solution: Upgrade to >=0.3.47 (try `cargo update -p time`)
    ├ time v0.3.41
      └── tracing-appender v0.2.3
          └── libdd-log v1.0.0
              └── (dev) libdd-data-pipeline v7.0.0

advisories FAILED, bans ok, sources ok

Updated: 2026-08-10 21:00:48 UTC | Commit: 4f0edce | dependency-check job results

pr-commenter · 2026-08-10T19:12:43Z

Benchmarks

Comparison

Benchmark execution time: 2026-08-10 21:09:44

Comparing candidate commit a07af01 in PR branch codex/trace-export-telemetry-metrics with baseline commit 130ed6b in branch main.

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 ----------------------------------'

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	`a07af01`	1786395425	codex/trace-export-telemetry-metrics

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.306ms	56.698ms ± 0.294ms	56.602ms ± 0.118ms	56.760ms	57.416ms	57.547ms	57.604ms	1.77%	1.415	1.198	0.52%	0.021ms	1	200
trace_buffer/1_senders/10us_delay	throughput	15624.025op/s	15874.014op/s ± 81.616op/s	15900.551op/s ± 33.358op/s	15927.533op/s	15954.335op/s	15974.059op/s	15984.123op/s	0.53%	-1.397	1.143	0.51%	5.771op/s	1	200
trace_buffer/1_senders/1us_delay	execution_time	50.022ms	50.085ms ± 0.027ms	50.080ms ± 0.010ms	50.091ms	50.138ms	50.150ms	50.195ms	0.23%	1.157	1.964	0.05%	0.002ms	1	200
trace_buffer/1_senders/1us_delay	throughput	17930.223op/s	17969.357op/s ± 9.571op/s	17971.204op/s ± 3.634op/s	17974.792op/s	17980.594op/s	17989.755op/s	17992.100op/s	0.12%	-1.153	1.952	0.05%	0.677op/s	1	200
trace_buffer/1_senders/no_delay	execution_time	333.266µs	341.101µs ± 3.498µs	340.945µs ± 1.718µs	342.750µs	346.073µs	351.742µs	356.128µs	4.45%	0.797	2.840	1.02%	0.247µs	1	200
trace_buffer/1_senders/no_delay	throughput	2527181.612op/s	2638784.918op/s ± 26855.508op/s	2639723.174op/s ± 13353.901op/s	2651993.501op/s	2684975.605op/s	2696943.156op/s	2700545.084op/s	2.30%	-0.671	2.475	1.02%	1898.971op/s	1	200
trace_buffer/2_senders/10us_delay	execution_time	56.892ms	57.270ms ± 0.145ms	57.267ms ± 0.096ms	57.363ms	57.525ms	57.605ms	57.749ms	0.84%	0.225	0.079	0.25%	0.010ms	1	200
trace_buffer/2_senders/10us_delay	throughput	31169.407op/s	31430.527op/s ± 79.803op/s	31431.484op/s ± 52.529op/s	31484.747op/s	31558.690op/s	31600.841op/s	31638.620op/s	0.66%	-0.210	0.065	0.25%	5.643op/s	1	200
trace_buffer/2_senders/1us_delay	execution_time	49.950ms	50.117ms ± 0.039ms	50.110ms ± 0.018ms	50.129ms	50.200ms	50.223ms	50.237ms	0.25%	0.543	2.229	0.08%	0.003ms	1	200
trace_buffer/2_senders/1us_delay	throughput	35830.516op/s	35916.233op/s ± 27.951op/s	35921.317op/s ± 12.758op/s	35931.796op/s	35950.851op/s	35960.276op/s	36035.701op/s	0.32%	-0.534	2.241	0.08%	1.976op/s	1	200
trace_buffer/2_senders/no_delay	execution_time	853.422µs	903.618µs ± 16.435µs	905.720µs ± 11.431µs	916.180µs	927.382µs	936.616µs	937.875µs	3.55%	-0.385	-0.167	1.81%	1.162µs	1	200
trace_buffer/2_senders/no_delay	throughput	1919232.421op/s	1992652.611op/s ± 36528.429op/s	1987368.148op/s ± 25194.161op/s	2015978.592op/s	2057572.428op/s	2085194.823op/s	2109154.747op/s	6.13%	0.478	-0.040	1.83%	2582.950op/s	1	200
trace_buffer/4_senders/10us_delay	execution_time	57.133ms	57.481ms ± 0.142ms	57.471ms ± 0.089ms	57.568ms	57.693ms	57.845ms	58.011ms	0.94%	0.421	0.590	0.25%	0.010ms	1	200
trace_buffer/4_senders/10us_delay	throughput	62057.454op/s	62629.781op/s ± 154.085op/s	62639.919op/s ± 96.697op/s	62718.556op/s	62866.657op/s	62930.826op/s	63010.734op/s	0.59%	-0.403	0.556	0.25%	10.895op/s	1	200
trace_buffer/4_senders/1us_delay	execution_time	50.119ms	50.165ms ± 0.036ms	50.156ms ± 0.019ms	50.178ms	50.243ms	50.282ms	50.300ms	0.29%	1.458	2.032	0.07%	0.003ms	1	200
trace_buffer/4_senders/1us_delay	throughput	71571.092op/s	71763.218op/s ± 50.989op/s	71775.595op/s ± 26.623op/s	71798.282op/s	71818.655op/s	71827.988op/s	71828.552op/s	0.07%	-1.454	2.017	0.07%	3.605op/s	1	200
trace_buffer/4_senders/no_delay	execution_time	2.185ms	2.406ms ± 0.083ms	2.419ms ± 0.061ms	2.469ms	2.518ms	2.557ms	2.602ms	7.57%	-0.260	-0.584	3.42%	0.006ms	1	200
trace_buffer/4_senders/no_delay	throughput	1383450.778op/s	1498292.029op/s ± 52013.350op/s	1488174.201op/s ± 36709.848op/s	1537556.911op/s	1592516.882op/s	1612056.290op/s	1647565.154op/s	10.71%	0.399	-0.484	3.46%	3677.899op/s	1	200
trace_buffer/8_senders/10us_delay	execution_time	57.638ms	57.948ms ± 0.186ms	57.900ms ± 0.114ms	58.066ms	58.317ms	58.403ms	58.518ms	1.07%	0.798	-0.123	0.32%	0.013ms	1	200
trace_buffer/8_senders/10us_delay	throughput	123038.876op/s	124250.491op/s ± 397.403op/s	124352.765op/s ± 245.384op/s	124570.790op/s	124737.075op/s	124873.655op/s	124918.560op/s	0.45%	-0.786	-0.147	0.32%	28.101op/s	1	200
trace_buffer/8_senders/1us_delay	execution_time	50.205ms	50.283ms ± 0.055ms	50.268ms ± 0.030ms	50.317ms	50.393ms	50.450ms	50.519ms	0.50%	1.261	1.737	0.11%	0.004ms	1	200
trace_buffer/8_senders/1us_delay	throughput	142521.279op/s	143188.743op/s ± 157.764op/s	143233.127op/s ± 85.091op/s	143295.172op/s	143370.140op/s	143405.810op/s	143411.925op/s	0.12%	-1.253	1.707	0.11%	11.156op/s	1	200
trace_buffer/8_senders/no_delay	execution_time	5.675ms	6.406ms ± 0.181ms	6.454ms ± 0.092ms	6.528ms	6.615ms	6.648ms	6.691ms	3.68%	-1.426	2.595	2.81%	0.013ms	1	200
trace_buffer/8_senders/no_delay	throughput	1076029.398op/s	1124790.827op/s ± 33169.589op/s	1115644.225op/s ± 15811.670op/s	1140044.807op/s	1185354.394op/s	1247190.470op/s	1268730.143op/s	13.72%	1.660	3.625	2.94%	2345.444op/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.657ms; 56.739ms] or [-0.072%; +0.072%]	None	None	None
trace_buffer/1_senders/10us_delay	throughput	[15862.703op/s; 15885.325op/s] or [-0.071%; +0.071%]	None	None	None
trace_buffer/1_senders/1us_delay	execution_time	[50.082ms; 50.089ms] or [-0.007%; +0.007%]	None	None	None
trace_buffer/1_senders/1us_delay	throughput	[17968.030op/s; 17970.683op/s] or [-0.007%; +0.007%]	None	None	None
trace_buffer/1_senders/no_delay	execution_time	[340.617µs; 341.586µs] or [-0.142%; +0.142%]	None	None	None
trace_buffer/1_senders/no_delay	throughput	[2635063.003op/s; 2642506.834op/s] or [-0.141%; +0.141%]	None	None	None
trace_buffer/2_senders/10us_delay	execution_time	[57.249ms; 57.290ms] or [-0.035%; +0.035%]	None	None	None
trace_buffer/2_senders/10us_delay	throughput	[31419.467op/s; 31441.587op/s] or [-0.035%; +0.035%]	None	None	None
trace_buffer/2_senders/1us_delay	execution_time	[50.111ms; 50.122ms] or [-0.011%; +0.011%]	None	None	None
trace_buffer/2_senders/1us_delay	throughput	[35912.359op/s; 35920.106op/s] or [-0.011%; +0.011%]	None	None	None
trace_buffer/2_senders/no_delay	execution_time	[901.340µs; 905.896µs] or [-0.252%; +0.252%]	None	None	None
trace_buffer/2_senders/no_delay	throughput	[1987590.122op/s; 1997715.100op/s] or [-0.254%; +0.254%]	None	None	None
trace_buffer/4_senders/10us_delay	execution_time	[57.461ms; 57.501ms] or [-0.034%; +0.034%]	None	None	None
trace_buffer/4_senders/10us_delay	throughput	[62608.426op/s; 62651.136op/s] or [-0.034%; +0.034%]	None	None	None
trace_buffer/4_senders/1us_delay	execution_time	[50.160ms; 50.170ms] or [-0.010%; +0.010%]	None	None	None
trace_buffer/4_senders/1us_delay	throughput	[71756.151op/s; 71770.285op/s] or [-0.010%; +0.010%]	None	None	None
trace_buffer/4_senders/no_delay	execution_time	[2.394ms; 2.417ms] or [-0.476%; +0.476%]	None	None	None
trace_buffer/4_senders/no_delay	throughput	[1491083.479op/s; 1505500.579op/s] or [-0.481%; +0.481%]	None	None	None
trace_buffer/8_senders/10us_delay	execution_time	[57.922ms; 57.974ms] or [-0.044%; +0.044%]	None	None	None
trace_buffer/8_senders/10us_delay	throughput	[124195.415op/s; 124305.568op/s] or [-0.044%; +0.044%]	None	None	None
trace_buffer/8_senders/1us_delay	execution_time	[50.276ms; 50.291ms] or [-0.015%; +0.015%]	None	None	None
trace_buffer/8_senders/1us_delay	throughput	[143166.879op/s; 143210.608op/s] or [-0.015%; +0.015%]	None	None	None
trace_buffer/8_senders/no_delay	execution_time	[6.381ms; 6.432ms] or [-0.391%; +0.391%]	None	None	None
trace_buffer/8_senders/no_delay	throughput	[1120193.841op/s; 1129387.813op/s] or [-0.409%; +0.409%]	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	`130ed6b`	1786380770	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	56.332ms	56.600ms ± 0.210ms	56.544ms ± 0.076ms	56.654ms	56.937ms	57.528ms	57.652ms	1.96%	2.644	9.073	0.37%	0.015ms	1	200
trace_buffer/1_senders/10us_delay	throughput	15610.871op/s	15901.317op/s ± 58.301op/s	15916.839op/s ± 21.355op/s	15935.211op/s	15956.178op/s	15972.219op/s	15976.638op/s	0.38%	-2.599	8.803	0.37%	4.123op/s	1	200
trace_buffer/1_senders/1us_delay	execution_time	49.954ms	50.080ms ± 0.031ms	50.080ms ± 0.009ms	50.086ms	50.138ms	50.195ms	50.206ms	0.25%	0.744	3.714	0.06%	0.002ms	1	200
trace_buffer/1_senders/1us_delay	throughput	17926.183op/s	17971.423op/s ± 11.279op/s	17971.221op/s ± 3.360op/s	17975.251op/s	17989.507op/s	17991.066op/s	18016.500op/s	0.25%	-0.734	3.705	0.06%	0.798op/s	1	200
trace_buffer/1_senders/no_delay	execution_time	330.487µs	337.987µs ± 5.499µs	337.386µs ± 1.431µs	338.892µs	342.855µs	350.491µs	402.187µs	19.21%	8.218	91.513	1.62%	0.389µs	1	200
trace_buffer/1_senders/no_delay	throughput	2237763.165op/s	2663443.279op/s ± 38571.305op/s	2667568.743op/s ± 11311.822op/s	2678381.035op/s	2697829.638op/s	2709120.649op/s	2723257.457op/s	2.09%	-7.032	72.947	1.44%	2727.403op/s	1	200
trace_buffer/2_senders/10us_delay	execution_time	56.497ms	56.920ms ± 0.199ms	56.893ms ± 0.117ms	57.012ms	57.290ms	57.496ms	57.690ms	1.40%	0.831	1.040	0.35%	0.014ms	1	200
trace_buffer/2_senders/10us_delay	throughput	31201.302op/s	31623.850op/s ± 110.227op/s	31638.610op/s ± 65.117op/s	31698.490op/s	31779.897op/s	31823.550op/s	31860.363op/s	0.70%	-0.806	0.980	0.35%	7.794op/s	1	200
trace_buffer/2_senders/1us_delay	execution_time	50.030ms	50.109ms ± 0.032ms	50.104ms ± 0.017ms	50.123ms	50.166ms	50.223ms	50.278ms	0.35%	1.504	4.740	0.06%	0.002ms	1	200
trace_buffer/2_senders/1us_delay	throughput	35800.611op/s	35921.481op/s ± 22.724op/s	35925.178op/s ± 12.299op/s	35936.464op/s	35947.326op/s	35954.665op/s	35978.542op/s	0.15%	-1.496	4.698	0.06%	1.607op/s	1	200
trace_buffer/2_senders/no_delay	execution_time	836.873µs	893.224µs ± 19.727µs	894.302µs ± 12.499µs	904.433µs	923.285µs	931.641µs	1000.064µs	11.83%	0.555	3.499	2.20%	1.395µs	1	200
trace_buffer/2_senders/no_delay	throughput	1799884.902op/s	2016141.652op/s ± 44141.325op/s	2012742.477op/s ± 28528.703op/s	2045250.517op/s	2087450.026op/s	2121149.401op/s	2150863.314op/s	6.86%	-0.247	2.306	2.18%	3121.263op/s	1	200
trace_buffer/4_senders/10us_delay	execution_time	57.216ms	57.488ms ± 0.137ms	57.473ms ± 0.087ms	57.564ms	57.741ms	57.878ms	57.941ms	0.81%	0.695	0.382	0.24%	0.010ms	1	200
trace_buffer/4_senders/10us_delay	throughput	62131.710op/s	62622.123op/s ± 148.811op/s	62637.694op/s ± 95.402op/s	62732.340op/s	62826.617op/s	62900.624op/s	62919.642op/s	0.45%	-0.682	0.356	0.24%	10.523op/s	1	200
trace_buffer/4_senders/1us_delay	execution_time	50.076ms	50.170ms ± 0.041ms	50.159ms ± 0.016ms	50.179ms	50.245ms	50.301ms	50.360ms	0.40%	1.627	3.679	0.08%	0.003ms	1	200
trace_buffer/4_senders/1us_delay	throughput	71485.519op/s	71756.529op/s ± 58.590op/s	71771.229op/s ± 23.315op/s	71789.739op/s	71823.182op/s	71843.729op/s	71890.258op/s	0.17%	-1.620	3.646	0.08%	4.143op/s	1	200
trace_buffer/4_senders/no_delay	execution_time	2.024ms	2.326ms ± 0.089ms	2.336ms ± 0.056ms	2.383ms	2.467ms	2.515ms	2.549ms	9.09%	-0.423	0.574	3.81%	0.006ms	1	200
trace_buffer/4_senders/no_delay	throughput	1412446.558op/s	1549796.123op/s ± 60515.539op/s	1540876.855op/s ± 36917.437op/s	1584390.754op/s	1654712.381op/s	1736884.787op/s	1778622.624op/s	15.43%	0.711	1.117	3.89%	4279.095op/s	1	200
trace_buffer/8_senders/10us_delay	execution_time	57.610ms	57.913ms ± 0.166ms	57.876ms ± 0.111ms	58.013ms	58.235ms	58.307ms	58.392ms	0.89%	0.734	-0.245	0.29%	0.012ms	1	200
trace_buffer/8_senders/10us_delay	throughput	123304.611op/s	124325.966op/s ± 356.093op/s	124404.916op/s ± 238.446op/s	124587.092op/s	124766.819op/s	124897.035op/s	124977.404op/s	0.46%	-0.724	-0.262	0.29%	25.180op/s	1	200
trace_buffer/8_senders/1us_delay	execution_time	50.162ms	50.309ms ± 0.074ms	50.286ms ± 0.038ms	50.354ms	50.463ms	50.527ms	50.603ms	0.63%	1.271	1.524	0.15%	0.005ms	1	200
trace_buffer/8_senders/1us_delay	throughput	142284.231op/s	143115.497op/s ± 209.511op/s	143182.119op/s ± 108.676op/s	143266.141op/s	143343.442op/s	143368.213op/s	143534.589op/s	0.25%	-1.263	1.494	0.15%	14.815op/s	1	200
trace_buffer/8_senders/no_delay	execution_time	5.718ms	6.442ms ± 0.159ms	6.469ms ± 0.107ms	6.565ms	6.648ms	6.677ms	6.700ms	3.58%	-0.996	1.611	2.45%	0.011ms	1	200
trace_buffer/8_senders/no_delay	throughput	1074552.235op/s	1118308.309op/s ± 28283.408op/s	1113003.997op/s ± 18199.687op/s	1134977.800op/s	1167412.401op/s	1198332.844op/s	1259100.572op/s	13.13%	1.210	2.609	2.52%	1999.939op/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.629ms] or [-0.051%; +0.051%]	None	None	None
trace_buffer/1_senders/10us_delay	throughput	[15893.237op/s; 15909.397op/s] or [-0.051%; +0.051%]	None	None	None
trace_buffer/1_senders/1us_delay	execution_time	[50.075ms; 50.084ms] or [-0.009%; +0.009%]	None	None	None
trace_buffer/1_senders/1us_delay	throughput	[17969.859op/s; 17972.986op/s] or [-0.009%; +0.009%]	None	None	None
trace_buffer/1_senders/no_delay	execution_time	[337.225µs; 338.750µs] or [-0.225%; +0.225%]	None	None	None
trace_buffer/1_senders/no_delay	throughput	[2658097.667op/s; 2668788.891op/s] or [-0.201%; +0.201%]	None	None	None
trace_buffer/2_senders/10us_delay	execution_time	[56.892ms; 56.947ms] or [-0.048%; +0.048%]	None	None	None
trace_buffer/2_senders/10us_delay	throughput	[31608.574op/s; 31639.126op/s] or [-0.048%; +0.048%]	None	None	None
trace_buffer/2_senders/1us_delay	execution_time	[50.105ms; 50.114ms] or [-0.009%; +0.009%]	None	None	None
trace_buffer/2_senders/1us_delay	throughput	[35918.332op/s; 35924.630op/s] or [-0.009%; +0.009%]	None	None	None
trace_buffer/2_senders/no_delay	execution_time	[890.490µs; 895.958µs] or [-0.306%; +0.306%]	None	None	None
trace_buffer/2_senders/no_delay	throughput	[2010024.089op/s; 2022259.216op/s] or [-0.303%; +0.303%]	None	None	None
trace_buffer/4_senders/10us_delay	execution_time	[57.469ms; 57.507ms] or [-0.033%; +0.033%]	None	None	None
trace_buffer/4_senders/10us_delay	throughput	[62601.499op/s; 62642.747op/s] or [-0.033%; +0.033%]	None	None	None
trace_buffer/4_senders/1us_delay	execution_time	[50.164ms; 50.175ms] or [-0.011%; +0.011%]	None	None	None
trace_buffer/4_senders/1us_delay	throughput	[71748.409op/s; 71764.649op/s] or [-0.011%; +0.011%]	None	None	None
trace_buffer/4_senders/no_delay	execution_time	[2.314ms; 2.339ms] or [-0.530%; +0.530%]	None	None	None
trace_buffer/4_senders/no_delay	throughput	[1541409.251op/s; 1558182.995op/s] or [-0.541%; +0.541%]	None	None	None
trace_buffer/8_senders/10us_delay	execution_time	[57.890ms; 57.936ms] or [-0.040%; +0.040%]	None	None	None
trace_buffer/8_senders/10us_delay	throughput	[124276.615op/s; 124375.317op/s] or [-0.040%; +0.040%]	None	None	None
trace_buffer/8_senders/1us_delay	execution_time	[50.299ms; 50.319ms] or [-0.020%; +0.020%]	None	None	None
trace_buffer/8_senders/1us_delay	throughput	[143086.461op/s; 143144.533op/s] or [-0.020%; +0.020%]	None	None	None
trace_buffer/8_senders/no_delay	execution_time	[6.420ms; 6.464ms] or [-0.341%; +0.341%]	None	None	None
trace_buffer/8_senders/no_delay	throughput	[1114388.500op/s; 1122228.117op/s] or [-0.351%; +0.351%]	None	None	None

datadog-datadog-prod-us1 · 2026-08-10T19:18:28Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 89.42%
• Overall Coverage: 76.05% (+0.06%)

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

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

dd-octo-sts · 2026-08-10T19:45:17Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.20 MB	8.20 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.19 MB	89.24 MB	+.06% (+56.32 KB) 🔍

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.06 MB	+.01% (+1.43 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.36 MB	100.41 MB	+.05% (+54.42 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.63 MB	26.64 MB	+.04% (+12.50 KB) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	191.41 MB	191.47 MB	+.02% (+56.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	1001.43 MB	1001.32 MB	--.01% (-112.24 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.71 MB	8.72 MB	+.08% (+8.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.62 MB	25.62 MB	+.03% (+8.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.01 MB	51.04 MB	+.05% (+30.93 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.22 MB	23.23 MB	+.05% (+13.00 KB) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	196.33 MB	196.40 MB	+.03% (+72.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	990.81 MB	990.47 MB	--.03% (-349.27 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.73 MB	6.74 MB	+.07% (+5.00 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.55 MB	27.56 MB	+.02% (+8.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.55 MB	48.58 MB	+.05% (+25.78 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.46 MB	79.51 MB	+.06% (+51.42 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.12 MB	9.13 MB	+.08% (+8.00 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.12 MB	95.17 MB	+.05% (+52.57 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.14 MB	11.15 MB	+.07% (+9.09 KB) 🔍

feat(data-pipeline): emit trace export telemetry metrics

befd1d0

github-actions Bot added the data-pipeline label Aug 10, 2026

mabdinur added 2 commits August 10, 2026 16:55

refactor(data-pipeline): preserve exporter visibility

a4070e1

refactor(data-pipeline): preserve mapper signature

a07af01

Navigation Menu

Uh oh!

feat(data-pipeline): emit native trace export telemetry - #2338

feat(data-pipeline): emit native trace export telemetry#2338
mabdinur wants to merge 3 commits into
mainfrom
codex/trace-export-telemetry-metrics

mabdinur commented Aug 10, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 10, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 10, 2026 •

edited

Loading

Uh oh!

pr-commenter Bot commented Aug 10, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Group 1

Group 1

Uh oh!

datadog-datadog-prod-us1 Bot commented Aug 10, 2026 •

edited by datadog-datadog-us1-prod Bot

Loading

Uh oh!

dd-octo-sts Bot commented Aug 10, 2026 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

mabdinur commented Aug 10, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Metrics

Implementation notes

Test plan

Uh oh!

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

Uh oh!

📚 Documentation Check Results

📦 libdd-data-pipeline - 1278 warning(s)

Uh oh!

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

Uh oh!

🔒 Cargo Deny Results

📦 libdd-data-pipeline - 3 error(s)

Uh oh!

pr-commenter Bot commented Aug 10, 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

Candidate

Group 1

Baseline

Group 1

Uh oh!

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

Uh oh!

Uh oh!

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

Uh oh!

Artifact Size Benchmark Report

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

mabdinur commented Aug 10, 2026 •

edited

Loading

github-actions Bot commented Aug 10, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 1278 warning(s)

github-actions Bot commented Aug 10, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 3 error(s)

pr-commenter Bot commented Aug 10, 2026 •

edited

Loading

datadog-datadog-prod-us1 Bot commented Aug 10, 2026 •

edited by datadog-datadog-us1-prod Bot

Loading

dd-octo-sts Bot commented Aug 10, 2026 •

edited

Loading