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. When dd-trace-py uses NativeWriter, libdatadog owns trace serialization and export, so it must emit the same writer telemetry.

This covers every native trace export path:

Agentless JSON
Agent v0.4, v0.5, and v1 msgpack
OTLP JSON and protobuf

Metrics

spans_enqueued_for_serialization when spans enter the native export pipeline
spans_dropped with reason:serialization_error when serialization definitively fails
spans_dropped with reason:api_error when transport definitively fails
Existing trace_api.* and trace-chunk telemetry extended to agentless and OTLP export

Pre-send serialization failures count both affected trace chunks and spans. Transport failures retain the existing chunk-drop reason while recording the corresponding span drop as api_error.

Retry and byte accounting

Transport helpers invoke a crate-internal observer once after the retry loop with the final SendWithRetryResult:

trace_api.requests reflects the total number of HTTP attempts.
Response, error, chunk, and span outcomes are recorded once per payload.
Retries never multiply chunk or span drop counts.

Existing send_agentless_traces_http, send_otlp_traces_http, and send_with_retry signatures and error behavior remain unchanged. The additive send_with_retry_and_size helper also returns the final post-compression payload size for agentless byte telemetry, matching the bytes placed on the wire without recompressing the payload.

Test plan

cargo check -p libdd-data-pipeline
cargo check -p libdd-data-pipeline --no-default-features
cargo +stable clippy -p libdd-data-pipeline --all-targets -- -D warnings
cargo +stable clippy -p libdd-data-pipeline --all-targets --features compression -- -D warnings
cargo +stable clippy -p libdd-trace-utils --all-targets --features compression -- -D warnings
cargo nextest run -p libdd-data-pipeline (169 passed)
cargo nextest run -p libdd-data-pipeline --features compression (169 passed)
cargo nextest run -p libdd-trace-utils --features compression (336 passed)
cargo test -p libdd-data-pipeline --doc (2 passed)
cargo test -p libdd-trace-utils --features compression --doc (30 passed, 1 ignored)
cargo +nightly-2026-07-26 fmt --all -- --check
git diff --check

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

Benchmarks

Comparison

Benchmark execution time: 2026-09-01 04:20:31

Comparing candidate commit 329ccdf in PR branch codex/trace-export-telemetry-metrics with baseline commit 8c3d06b in branch main.

Found 2 performance improvements and 0 performance regressions! Performance is the same for 139 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 ----------------------------------'

scenario:msgpack_decoder::v05/high_sharing/200

🟩 execution_time [-9.810µs; -9.678µs] or [-5.836%; -5.758%]
🟩 throughput [+72720.178op/s; +73723.426op/s] or [+6.112%; +6.196%]

Benchmark execution time: 2026-09-01 04:16:59

Comparing candidate commit 329ccdf in PR branch codex/trace-export-telemetry-metrics with baseline commit 8c3d06b in branch main.

Found 2 performance improvements and 1 performance regressions! Performance is the same for 72 metrics, 10 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 ----------------------------------'

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

🟥 execution_time [+1.763ns; +1.782ns] or [+4.781%; +4.831%]

scenario:trace_buffer/2_senders/no_delay

🟩 execution_time [-89.048µs; -72.839µs] or [-5.437%; -4.447%]
🟩 throughput [+51295.547op/s; +62597.991op/s] or [+4.664%; +5.692%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

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

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 83.33%
• Overall Coverage: 76.92% (-0.03%)

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

🔗 Commit SHA: 329ccdf | Docs | View more details | 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.a	90.77 MB	90.86 MB	+.09% (+87.17 KB) 🔍
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.39 MB	8.39 MB	0% (0 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	101.99 MB	102.07 MB	+.08% (+86.91 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.29 MB	11.29 MB	+.03% (+3.61 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	27.03 MB	27.07 MB	+.13% (+37.00 KB) 🔍
/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	181.70 MB	181.94 MB	+.12% (+240.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	766.69 MB	768.24 MB	+.20% (+1.54 MB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.91 MB	8.95 MB	+.41% (+37.50 KB) 🔍
/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	26.05 MB	26.07 MB	+.08% (+24.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.84 MB	51.93 MB	+.17% (+91.60 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.57 MB	23.60 MB	+.12% (+30.00 KB) 🔍
/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	186.76 MB	187.02 MB	+.13% (+264.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	754.57 MB	755.32 MB	+.10% (+773.42 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.88 MB	6.91 MB	+.32% (+23.00 KB) 🔍
/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	28.00 MB	28.02 MB	+.08% (+24.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	49.34 MB	49.41 MB	+.14% (+74.72 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	80.93 MB	81.02 MB	+.10% (+87.11 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.33 MB	9.34 MB	+.12% (+12.00 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	96.69 MB	96.78 MB	+.08% (+88.76 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.37 MB	11.38 MB	+.13% (+15.60 KB) 🔍

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a07af01a22

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

mabdinur · 2026-08-25T14:43:16Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 45359c6565

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

mabdinur · 2026-09-01T17:37:40Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-09-01T17:37:45Z

View all feedbacks in Devflow UI.

2026-09-01 17:37:45 UTC ℹ️ Start processing command /merge

2026-09-01 17:37:52 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

Run /code blockers to see what is blocking it.
Run /remove to cancel it.

2026-09-01 21:52:08 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

mabdinur · 2026-09-01T21:58:36Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-09-01T21:58:40Z

View all feedbacks in Devflow UI.

2026-09-01 21:58:40 UTC ℹ️ Start processing command /merge

2026-09-01 21:58:47 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

Run /code blockers to see what is blocking it.
Run /remove to cancel it.

2026-09-02 02:11:28 UTC ⚠️ MergeQueue: This merge request was unqueued

devflow unqueued this merge request: It did not become mergeable within the expected time

mabdinur · 2026-09-02T04:26:33Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-09-02T04:26:38Z

View all feedbacks in Devflow UI.

2026-09-02 04:26:38 UTC ℹ️ Start processing command /merge

2026-09-02 04:26:48 UTC ℹ️ MergeQueue: Pull request is not mergeable yet

It will be processed automatically as soon as GitHub reports it as mergeable. View in MergeQueue UI.

Run /code blockers to see what is blocking it.
Run /remove to cancel it.

2026-09-02 07:56:16 UTC ℹ️ MergeQueue: merge request added to the queue

The expected merge time in main is approximately 49m (p90).

2026-09-02 08:34:11 UTC ℹ️ MergeQueue: This merge request was merged

…ker, libdd-data-pipeline, li... (#2482) # Release proposal for libdd-capabilities-impl, libdd-crashtracker, libdd-data-pipeline, libdd-ddsketch, libdd-ffe, libdd-http-client, libdd-ipc, libdd-library-config, libdd-live-debugger, libdd-otel-thread-ctx, libdd-remote-config, libdd-shared-runtime, libdd-telemetry, libdd-trace-utils, libdd-tracer-flare 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-common` `5.2.0` → `6.0.0` affects: `libdd-profiling`, `libdd-sampling` - `libdd-trace-utils` `11.0.0` → `12.0.0` affects: `libdd-sampling` ## libdd-capabilities **Next version:** `3.0.1` **Semver bump:** `patch` **Tag:** `libdd-capabilities-v3.0.1` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) ## libdd-common **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-common-v6.0.0` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421) ## libdd-ipc-macros **Next version:** `1.0.1` **Semver bump:** `patch` **Tag:** `libdd-ipc-macros-v1.0.1` ### Commits - feat(sidecar)!: support appsec helper-rust integration with sidecar (#2310) ## libdd-otel-thread-ctx **Next version:** `1.1.0` **Semver bump:** `minor` **Tag:** `libdd-otel-thread-ctx-v1.1.0` ### Commits - feat(otel-thread-ctx): add update-and-attach operation (#2443) ## libdd-tinybytes **Next version:** `1.1.3` **Semver bump:** `patch` **Tag:** `libdd-tinybytes-v1.1.3` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-capabilities-impl **Next version:** `5.0.0` **Semver bump:** `major` **Tag:** `libdd-capabilities-impl-v5.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) - feat(data-pipeline): add runtime-independent agentless sending (#2389) ## libdd-http-client **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-http-client-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421) ## libdd-remote-config **Next version:** `5.0.0` **Semver bump:** `major` **Tag:** `libdd-remote-config-v5.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - fix(remote-config): refresh fetcher identity (#2469) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(remote-config): reuse injected sleep capability (#2429) ## libdd-shared-runtime **Next version:** `4.0.0` **Semver bump:** `major` **Tag:** `libdd-shared-runtime-v4.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - fix(shared-runtime): allow disabling worker fork restart (#2464) ## libdd-trace-utils **Next version:** `12.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-utils-v12.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - feat(trace-utils): add v1-native JSON log encoder brick (#2371) - feat(trace-utils): add v1-native agentless JSON encoder brick (#2370) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - feat(data-pipeline): emit native trace export telemetry (#2338) - feat(data-pipeline)!: add agentless stats export (#2309) - fix(trace-utils): use vec map dedup when serializing (#2422) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - fix(compression): align zstd behavior across targets (#2400) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-ffe **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-ffe-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 - `libdd-remote-config`: ^3.0.0 → ^4.1.0 - `libdd-trace-protobuf`: ^4.0.1 → ^5.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(ffe): support arbitrary semver core parts (#2413) - feat(ffe)!: send the split serial id on exposure events [EX-3425] (#2402) - feat(ffe): expose observeFullEvaluationData config-level FFI getter (#2373) - fix(ffe): report rejected flags as parse errors (#2339) - test: skip/shorten slow miri jobs (#2331) ## libdd-dogstatsd-client **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-dogstatsd-client-v6.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-telemetry **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-telemetry-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - refactor(telemetry): avoid doing two separate http requests in stop telemetry (#2435) ## libdd-trace-obfuscation **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-obfuscation-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - fix(trace-obfuscation): scan all span meta for credit-card obfuscation (#2472) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418) ## libdd-tracer-flare **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-tracer-flare-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-crashtracker **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(crashtracking): filter out frames above faulting frame (#2428) - feat(sidecar)!: support appsec helper-rust integration with sidecar (#2310) - chore(crashtracking): use RAII remote ptrace API (#2416) - chore(crashtracking): bump libdd-libunwind-sys to v1.0.3 (#2414) ## libdd-data-pipeline-core **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-core-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. ## libdd-trace-stats **Next version:** `9.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-stats-v9.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-data-pipeline **Next version:** `10.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-v10.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0 - `libdd-trace-stats`: ^8.0.0 → ^9.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - feat(trace-utils): add v1-native JSON log encoder brick (#2371) - chore: prepare crate for publishing (#2466) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - fix(data-pipeline): pass obfuscation config to OTLP stats (#2444) - feat(data-pipeline): emit native trace export telemetry (#2338) - feat(data-pipeline): add fork-safe OTLP gRPC trace transport (#2273) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-ipc **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-ipc-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-stats`: ^8.0.0 → ^9.0.0 ### Commits - fix(ipc): drop the signal feature from libdd-ipc (#2431) ## libdd-live-debugger **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-live-debugger-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. [EX-3425]: https://datadoghq.atlassian.net/browse/EX-3425?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: hoolioh <107922352+hoolioh@users.noreply.github.com>

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

mabdinur marked this pull request as ready for review August 19, 2026 14:08

mabdinur requested review from a team as code owners August 19, 2026 14:08

mabdinur requested review from vpellan and removed request for a team August 19, 2026 14:08

chatgpt-codex-connector Bot reviewed Aug 19, 2026

View reviewed changes

Comment thread libdd-data-pipeline/src/agentless/exporter.rs Outdated

Comment thread libdd-data-pipeline/src/trace_exporter/mod.rs Outdated

Comment thread libdd-data-pipeline/src/trace_exporter/mod.rs Outdated

mabdinur requested a review from a team as a code owner August 20, 2026 13:42

github-actions Bot added the mini-agent label Aug 20, 2026

fix(data-pipeline): preserve trace transport behavior

3b00525

mabdinur force-pushed the codex/trace-export-telemetry-metrics branch from b827abc to 3b00525 Compare August 20, 2026 14:17

Aaalibaba42 requested changes Aug 25, 2026

View reviewed changes

Comment thread libdd-data-pipeline/src/trace_exporter/mod.rs Outdated

fix(data-pipeline): count spans after export filtering

6c0dae8

mabdinur requested a review from Aaalibaba42 August 25, 2026 14:04

refactor(data-pipeline): centralize payload telemetry counts

45359c6

mabdinur requested review from a team, Aaalibaba42 and vpellan and removed request for a team, Aaalibaba42 and vpellan August 25, 2026 14:43

chatgpt-codex-connector Bot reviewed Aug 25, 2026

View reviewed changes

Comment thread libdd-data-pipeline/src/trace_exporter/mod.rs Outdated

refactor(data-pipeline): reduce telemetry accounting diff

8c9d3fc

gh-worker-dd-devflow-36fce6 Bot added the mergequeue-status: removed label Sep 1, 2026

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: waiting mergequeue-status: removed and removed mergequeue-status: removed mergequeue-status: waiting labels Sep 1, 2026

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: waiting and removed mergequeue-status: removed labels Sep 2, 2026

vpellan approved these changes Sep 2, 2026

View reviewed changes

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: queued mergequeue-status: in_progress and removed mergequeue-status: waiting mergequeue-status: queued labels Sep 2, 2026

gh-worker-dd-mergequeue-cf854d Bot merged commit 1887a57 into main Sep 2, 2026
315 of 317 checks passed

gh-worker-dd-devflow-36fce6 Bot removed the mergequeue-status: in_progress label Sep 2, 2026

gh-worker-dd-mergequeue-cf854d Bot deleted the codex/trace-export-telemetry-metrics branch September 2, 2026 08:34

gh-worker-dd-devflow-36fce6 Bot added the mergequeue-status: done label Sep 2, 2026

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

Retry and byte accounting

Test plan

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

scenario:msgpack_decoder::v05/high_sharing/200

Explanation

More details about the CI and significant changes

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

scenario:trace_buffer/2_senders/no_delay

Candidate

Baseline

Uh oh!

datadog-datadog-prod-us1 Bot commented Aug 10, 2026 • edited by datadog-datadog-prod-us1-2 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!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

mabdinur commented Aug 25, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

mabdinur commented Sep 1, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Sep 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mabdinur commented Sep 1, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Sep 1, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mabdinur commented Sep 2, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Sep 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

mabdinur commented Aug 10, 2026 •

edited

Loading

pr-commenter Bot commented Aug 10, 2026 •

edited

Loading

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

edited by datadog-datadog-prod-us1-2 Bot

Loading

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

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Sep 1, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Sep 1, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Sep 2, 2026 •

edited

Loading