feat(data-pipeline): adds new attributes to OTLP trace metrics export by mabdinur · Pull Request #2316 · DataDog/libdatadog

mabdinur · 2026-08-04T19:43:46Z

What does this PR do?

Adds the libdatadog OTLP trace-metrics support used by ddtrace-py.

Exports canonical SMC dimensions plus available HTTP, RPC, and Datadog data-point attributes.
Emits trace-root and top-level values as booleans and peer tags as an array.
Adds runtime ID, process tags, and tracer tags to resource attributes.
Adds builder configuration for tracer tags and additional metric tag keys.
Omits optional method, route, span type, and service-source attributes when unset.
Keeps trace-metrics output independent of OTel-semantics mode without changing configuration parsing.

Motivation

ddtrace-py needs the shared exporter to implement the contract defined in system-tests#7363 and refined in system-tests#7466.

Additional Notes

Includes a release note announcing ddtrace-py support.

How to test the change?

Rust formatting, cargo check, Clippy, data-pipeline tests, trace-utils tests, and ddtrace-py OTLP system tests passed.

Fixes several OTLP Span Metrics Connector attribute conventions on the `traces.span.sdk.metrics.duration` histogram export: - process_tags/peer_tags: emit as a single `datadog.{process,peer}_tags` arrayValue instead of fanning out per-key attributes. - is_trace_root: rename `_datadog.is_trace_root` to `datadog.is_trace_root` and always emit true/false rather than only when true. - span.kind: canonicalize to the OTel SMC uppercase convention (e.g. `SPAN_KIND_SERVER`) instead of the raw Datadog tag value. - status.code: emit the SMC string convention (`STATUS_CODE_OK`/ `STATUS_CODE_ERROR`) unconditionally on every data point, replacing the int enum that was only set on error. Companion system-tests spec: DataDog/system-tests#7363

datadog-datadog-prod-us1 · 2026-08-04T19:57:18Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 93.36%
• Overall Coverage: 75.98% (+0.03%)

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

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

pr-commenter · 2026-08-04T20:21:05Z

Benchmarks

Comparison

Benchmark execution time: 2026-08-12 14:43:35

Comparing candidate commit 9890ff2 in PR branch munir/otlp-trace-metrics-fixes with baseline commit 7ba36d7 in branch main.

Found 13 performance improvements and 6 performance regressions! Performance is the same for 120 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:credit_card/is_card_number/x371413321323331

🟥 execution_time [+401.088ns; +403.697ns] or [+6.630%; +6.673%]
🟥 throughput [-10342903.954op/s; -10276104.648op/s] or [-6.257%; -6.217%]

scenario:credit_card/is_card_number_no_luhn/x371413321323331

🟥 execution_time [+401.162ns; +403.805ns] or [+6.630%; +6.674%]
🟥 throughput [-10342350.198op/s; -10274781.977op/s] or [-6.258%; -6.217%]

scenario:otlp/e2e_json/1x1000

🟥 execution_time [+346.393µs; +349.176µs] or [+8.682%; +8.751%]

scenario:otlp/encode_json/1x1000

🟥 execution_time [+316.650µs; +318.156µs] or [+18.724%; +18.813%]

scenario:vec_map/dedup/dup_1_in_10/16

🟩 execution_time [-43.747ns; -33.847ns] or [-5.304%; -4.104%]

scenario:vec_map/get_hit/128

🟩 execution_time [-3.287µs; -3.279µs] or [-19.978%; -19.928%]
🟩 throughput [+1936950.441op/s; +1941599.051op/s] or [+24.896%; +24.956%]

scenario:vec_map/get_hit/16

🟩 execution_time [-48.950ns; -48.807ns] or [-19.607%; -19.550%]
🟩 throughput [+15578116.087op/s; +15626838.643op/s] or [+24.307%; +24.383%]

scenario:vec_map/get_hit/64

🟩 execution_time [-777.244ns; -774.423ns] or [-17.744%; -17.680%]
🟩 throughput [+3139101.960op/s; +3150735.895op/s] or [+21.485%; +21.564%]

scenario:vec_map/get_hit/8

🟩 execution_time [-12.494ns; -12.446ns] or [-18.801%; -18.729%]
🟩 throughput [+27758302.488op/s; +27857422.962op/s] or [+23.058%; +23.140%]

scenario:vec_map/iter/128

🟩 execution_time [-6.740ns; -6.656ns] or [-6.086%; -6.010%]
🟩 throughput [+73937503.801op/s; +74885016.246op/s] or [+6.397%; +6.479%]

scenario:vec_map/iter/8

🟩 execution_time [-0.570ns; -0.558ns] or [-7.867%; -7.701%]
🟩 throughput [+92231320.564op/s; +94267175.427op/s] or [+8.353%; +8.537%]

Benchmark execution time: 2026-08-12 14:40:36

Comparing candidate commit 9890ff2 in PR branch munir/otlp-trace-metrics-fixes with baseline commit 7ba36d7 in branch main.

Found 8 performance improvements and 3 performance regressions! Performance is the same for 64 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:datadog_sample_span/complex_rule_matching/wall_time

🟩 execution_time [-26.262ns; -25.995ns] or [-4.309%; -4.265%]

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

🟩 execution_time [-1.758ns; -1.713ns] or [-6.194%; -6.034%]

scenario:glob_matcher/ascii_exact_match/wall_time

🟩 execution_time [-1.577ns; -1.519ns] or [-5.533%; -5.330%]

scenario:glob_matcher/ascii_exact_miss/wall_time

🟩 execution_time [-1.714ns; -1.665ns] or [-12.669%; -12.306%]

scenario:glob_matcher/unicode_exact_match/wall_time

🟩 execution_time [-6.470ns; -6.416ns] or [-7.966%; -7.900%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

🟥 execution_time [+3.919ns; +3.981ns] or [+4.343%; +4.412%]

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

🟩 execution_time [-6.357ns; -6.236ns] or [-4.823%; -4.732%]

scenario:trace_buffer/4_senders/no_delay

🟩 execution_time [-147.216µs; -122.654µs] or [-5.888%; -4.906%]
🟩 throughput [+74662.599op/s; +89749.999op/s] or [+5.182%; +6.229%]

scenario:trace_buffer/8_senders/no_delay

🟥 execution_time [+281.941µs; +324.354µs] or [+4.400%; +5.062%]
🟥 throughput [-54869.635op/s; -47400.865op/s] or [-4.881%; -4.216%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

dd-octo-sts · 2026-08-04T20:34:06Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

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

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.06 MB	+0% (+1.10 KB) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.37 MB	100.48 MB	+.10% (+112.95 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.63 MB	26.65 MB	+.07% (+20.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.42 MB	191.53 MB	+.05% (+112.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	1001.70 MB	1001.86 MB	+.01% (+165.67 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.71 MB	8.72 MB	+.12% (+11.50 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.64 MB	+.09% (+24.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.01 MB	51.06 MB	+.09% (+50.05 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.22 MB	23.24 MB	+.09% (+22.50 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.34 MB	196.47 MB	+.06% (+128.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	990.83 MB	991.07 MB	+.02% (+241.21 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.73 MB	6.74 MB	+.10% (+7.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.58 MB	+.08% (+24.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.56 MB	48.60 MB	+.09% (+46.74 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.47 MB	79.56 MB	+.11% (+90.61 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.13 MB	9.13 MB	+.04% (+4.00 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.12 MB	95.21 MB	+.09% (+91.36 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.14 MB	11.15 MB	+.04% (+4.60 KB) 🔍

Always emit available Datadog attributes for OTLP trace metrics and map non-empty service_source values to datadog.svc_src. BREAKING CHANGE: OtlpMetricsConfig and map_stats_to_otlp_metrics no longer accept the OTel trace-semantics setting.

Retain the OTel semantics field and mapper argument for downstream callers while keeping OTLP trace-metrics output unconditional.

…ics-fixes

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 78ce6ff5a2

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

vpellan

LGTM with minor comments

# Release proposal for libdd-sampling and its dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-common **Next version:** `5.2.0` **Semver bump:** `minor` **Tag:** `libdd-common-v5.2.0` ### Commits - feat(remote-config)!: agentless RC fetcher (#2112) - feat(common): allocation-free tag validation and parsing (#2329) ## libdd-trace-utils **Next version:** `10.1.0` **Semver bump:** `minor` **Tag:** `libdd-trace-utils-v10.1.0` ### Commits - feat(data-pipeline): adds new attributes to OTLP trace metrics export (#2316) - feat: add v1 isolated bricks for trace exporter (#2280) ## libdd-sampling **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-sampling-v6.0.0` ### ⚠️ major bump forced due to: - `libdd-trace-utils`: ^9.0.0 → ^10.1.0 ### Commits - feat(sampling): OTel consistent-probability rv/th derivation (APMAPI-2181) (#2276) - fix(sampling): record rate limiter's effective rate on allow, not just drop (#2288) - refactor: migrate to workspace dependencies, phase 4 (#2296) - chore: moving to workspace-level dependencies, phase 2 (#2270) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: hoolioh <107922352+hoolioh@users.noreply.github.com>

) # Release proposal for libdd-data-pipeline, libdd-telemetry and their dependencies This PR contains version bumps based on public API changes and commits since last release. ## libdd-ddsketch **Next version:** `1.1.1` **Semver bump:** `patch` **Tag:** `libdd-ddsketch-v1.1.1` ### Commits - refactor: migrate to workspace dependencies, phase 4 (#2296) - chore: moving to workspace-level dependencies, phase 2 (#2270) ## libdd-shared-runtime **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-shared-runtime-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-capabilities`: ^2.1.0 → ^3.0.0 - `libdd-capabilities-impl`: ^3.0.0 → ^4.0.0 ### Commits - feat(shared-runtime): add block_on_with_timeout to BlockingRuntime (#2333) - chore(runtime): restart all workers on invalid state (#2262) - refactor: migrate to workspace dependencies, phase 3 (#2283) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) ## libdd-dogstatsd-client **Next version:** `5.0.0` **Semver bump:** `major` **Tag:** `libdd-dogstatsd-client-v5.0.0` ### Commits - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat(dogstatsd)!: add shared_runtime buffered sink (#2224) - refactor(statsd)!: make client clonable (#2222) ## libdd-telemetry **Next version:** `7.0.0` **Semver bump:** `major` **Tag:** `libdd-telemetry-v7.0.0` ### Commits - refactor(rc)!: make conversion from RemoteConfigProduct back and forth generally available (#2325) - feat(telemetry)!: Add Installation signature and AppProduct changes payloads (#2213) - fix(telemetry)!: stop sending Connection: close to the Agent (#2286) - refactor: migrate to workspace dependencies, phase 3 (#2283) - chore: moving to workspace-level dependencies, phase 2 (#2270) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - fix: drain the mailbox before stopping (#2258) - feat(telemetry)!: make telemetry worker wasm-compatible for the TraceExporter (#2172) - fix(sidecar): don't double-encode file:// telemetry endpoints (#2230) ## libdd-trace-obfuscation **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-obfuscation-v6.0.0` ### ⚠️ major bump forced due to: - `libdd-trace-utils`: ^9.0.0 → ^10.1.0 ### Commits - refactor: migrate to workspace dependencies, phase 4 (#2296) - chore(lint): update nightly (#2281) - chore: moving to workspace-level dependencies, phase 2 (#2270) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - fix: new clippy lints (#2219) ## libdd-trace-stats **Next version:** `7.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-stats-v7.0.0` ### ⚠️ major bump forced due to: - `libdd-capabilities`: ^2.1.0 → ^3.0.0 - `libdd-capabilities-impl`: ^3.0.0 → ^4.0.0 - `libdd-dogstatsd-client`: ^4.0.0 → ^5.0.0 - `libdd-telemetry`: ^6.0.0 → ^7.0.0 - `libdd-trace-utils`: ^9.0.0 → ^10.1.0 ### Commits - feat: add v1 isolated bricks for trace exporter (#2280) - refactor: migrate to workspace dependencies, phase 4 (#2296) - feat(data-pipeline)!: add compression option for agentless export (#2205) - feat(stats)!: per-field cardinality limits (#2211) - refactor: migrate to workspace dependencies, phase 3 (#2283) - feat(stats)!: string field length limit (#2267) - feat(trace_exporter)!: add `restart_after_fork` configuration option [APMSP-3843] (#2263) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat(stats)!: implement additional metric tags in libdd-trace-stats (#2170) - refactor(statsd)!: make client clonable (#2222) - fix(stats-exporter): disable retries for stats payload sends (#2249) - feat(telemetry)!: make telemetry worker wasm-compatible for the TraceExporter (#2172) - fix!: css obfuscation logic (#2203) ## libdd-data-pipeline **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-capabilities`: ^2.1.0 → ^3.0.0 - `libdd-capabilities-impl`: ^3.0.0 → ^4.0.0 - `libdd-dogstatsd-client`: ^4.0.0 → ^5.0.0 - `libdd-telemetry`: ^6.0.0 → ^7.0.0 - `libdd-trace-stats`: ^6.0.0 → ^7.0.0 - `libdd-trace-utils`: ^9.0.0 → ^10.1.0 ### Commits - fix(trace-exporter): mark OTLP client-computed stats (#2245) - feat(data-pipeline): adds new attributes to OTLP trace metrics export (#2316) - feat: add v1 isolated bricks for trace exporter (#2280) - feat(data-pipeline)!: add flush_and_close to the trace buffer (#2313) - feat(telemetry)!: Add Installation signature and AppProduct changes payloads (#2213) - refactor: migrate to workspace dependencies, phase 4 (#2296) - feat(data-pipeline)!: add compression option for agentless export (#2205) - fix(telemetry)!: stop sending Connection: close to the Agent (#2286) - feat(stats)!: per-field cardinality limits (#2211) - refactor: migrate to workspace dependencies, phase 3 (#2283) - feat(stats)!: string field length limit (#2267) - refactor(trace-utils)!: split generic TracerHeaderTags (#2279) - chore: moving to workspace-level dependencies, phase 2 (#2270) - feat(trace_exporter)!: add `restart_after_fork` configuration option [APMSP-3843] (#2263) - feat(data-pipeline): emit additional_metric_tags on OTLP span duration metric (#2264) - refactor: consolidate core dependencies at workspace level (phase 1) (#2253) - feat(dogstatsd)!: add shared_runtime buffered sink (#2224) - feat(stats)!: implement additional metric tags in libdd-trace-stats (#2170) - refactor(statsd)!: make client clonable (#2222) - feat(telemetry)!: make telemetry worker wasm-compatible for the TraceExporter (#2172) - feat(trace_exporter)!: remove deprecated methods (#2250) - feat(trace-utils)!: add v1 decoder (#2174) - feat(trace-utils)!: add encoder v1 to v04 + refactor (#2145) - feat(otlp): add instrumentation scope metadata (#2235) - fix(trace-utils)!: serialize v0.5 span links and events into meta (#980) - fix!: css obfuscation logic (#2203) - test(data-pipeline): gate telemetry-only tests behind the telemetry feature (#2204) [APMSP-3843]: https://datadoghq.atlassian.net/browse/APMSP-3843?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>

mabdinur added the AI Generated PR largely written by AI tools label Aug 4, 2026

github-actions Bot added mini-agent data-pipeline labels Aug 4, 2026

mabdinur mentioned this pull request Aug 5, 2026

test(otlp-trace-metrics): maintain parity with the OTEP spec DataDog/system-tests#7363

Merged

2 tasks

mabdinur added 5 commits August 5, 2026 19:25

fix(data-pipeline): finalize OTLP trace metrics semantics

8ee6f7e

fix(data-pipeline): preserve OTel trace metric attributes

130a4de

fix(data-pipeline): reserve only datadog OTLP attributes

2e2e3cb

test(data-pipeline): cover unknown trace-root values

d7108bf

mabdinur changed the title ~~fix(data-pipeline): correct OTLP trace-metrics attribute shapes~~ fix(data-pipeline)!: make OTLP trace metrics mode-independent Aug 6, 2026

fix(data-pipeline): preserve metrics config compatibility

db88591

Retain the OTel semantics field and mapper argument for downstream callers while keeping OTLP trace-metrics output unconditional.

mabdinur changed the title ~~fix(data-pipeline)!: make OTLP trace metrics mode-independent~~ fix(data-pipeline): make OTLP trace metrics mode-independent Aug 6, 2026

mabdinur added 2 commits August 6, 2026 15:00

fix(data-pipeline): default unknown metric span kinds

f0ac2a2

fix(data-pipeline): decouple metrics exporter config

b3945ed

mabdinur mentioned this pull request Aug 6, 2026

test(otlp-trace-metrics): align cross-tracer attributes DataDog/system-tests#7466

Merged

refactor(data-pipeline): simplify OTLP metric mapping

e599898

github-actions Bot removed the mini-agent label Aug 7, 2026

refactor(data-pipeline): align OTLP metric attribute order

bfef125

mabdinur mentioned this pull request Aug 7, 2026

build(native): update libdatadog to v41.0.0 DataDog/dd-trace-py#19580

Merged

mabdinur added 3 commits August 7, 2026 11:18

refactor(data-pipeline): remove unused OTLP mapper option

0034e1b

Merge remote-tracking branch 'origin/main' into munir/otlp-trace-metr…

81bf31c

…ics-fixes

feat(data-pipeline): support OTLP trace metrics for ddtrace-py

78ce6ff

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

mabdinur changed the title ~~fix(data-pipeline): make OTLP trace metrics mode-independent~~ feat(data-pipeline): support OTLP trace metrics for ddtrace-py Aug 10, 2026

mabdinur changed the title ~~feat(data-pipeline): support OTLP trace metrics for ddtrace-py~~ feat(data-pipeline): support ddtrace-py OTLP trace metrics Aug 10, 2026

mabdinur marked this pull request as ready for review August 10, 2026 20:34

mabdinur requested review from a team as code owners August 10, 2026 20:34

mabdinur requested review from vpellan and removed request for a team August 10, 2026 20:34

chatgpt-codex-connector Bot reviewed Aug 10, 2026

View reviewed changes

Comment thread libdd-data-pipeline/src/otlp/metrics.rs

Comment thread libdd-data-pipeline/src/otlp/metrics.rs Outdated

Comment thread libdd-data-pipeline/src/otlp/config.rs

fix(data-pipeline): preserve OTLP metric attribute contracts

5961433

mabdinur changed the title ~~feat(data-pipeline): support ddtrace-py OTLP trace metrics~~ feat(data-pipeline): ensure OTLP trace metrics attributes are consistent with system tests Aug 11, 2026

mabdinur changed the title ~~feat(data-pipeline): ensure OTLP trace metrics attributes are consistent with system tests~~ feat(data-pipeline): revamps support for OTLP trace metrics export Aug 11, 2026

mabdinur changed the title ~~feat(data-pipeline): revamps support for OTLP trace metrics export~~ feat(data-pipeline): adds new attributes to OTLP trace metrics export Aug 11, 2026

vpellan approved these changes Aug 12, 2026

View reviewed changes

Comment thread libdd-data-pipeline/src/otlp/metrics.rs Outdated

mabdinur force-pushed the munir/otlp-trace-metrics-fixes branch from eb92491 to b0f7708 Compare August 12, 2026 14:11

refactor(data-pipeline): clarify optional OTLP attributes

9890ff2

mabdinur force-pushed the munir/otlp-trace-metrics-fixes branch from b0f7708 to 9890ff2 Compare August 12, 2026 14:13

mabdinur requested a review from VianneyRuhlmann August 12, 2026 14:29

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: queued mergequeue-status: in_progress and removed mergequeue-status: queued labels Aug 12, 2026

gh-worker-dd-mergequeue-cf854d Bot merged commit 0b8ca65 into main Aug 12, 2026
91 checks passed

gh-worker-dd-mergequeue-cf854d Bot deleted the munir/otlp-trace-metrics-fixes branch August 12, 2026 16:01

gh-worker-dd-devflow-36fce6 Bot added mergequeue-status: done and removed mergequeue-status: in_progress labels Aug 12, 2026

mabdinur mentioned this pull request Aug 12, 2026

chore: release v41.0.0 #2349

Merged

dd-octo-sts Bot mentioned this pull request Aug 17, 2026

chore(release): proposal for libdd-sampling #2355

Merged

dd-octo-sts Bot mentioned this pull request Aug 17, 2026

chore(release): proposal for libdd-data-pipeline, libdd-telemetry #2358

Merged

mabdinur mentioned this pull request Aug 21, 2026

Enable merged OTLP trace metrics coverage DataDog/system-tests#7563

Merged

5 tasks

Navigation Menu

Uh oh!

feat(data-pipeline): adds new attributes to OTLP trace metrics export - #2316

feat(data-pipeline): adds new attributes to OTLP trace metrics export#2316
gh-worker-dd-mergequeue-cf854d[bot] merged 16 commits into
mainfrom
munir/otlp-trace-metrics-fixes

mabdinur commented Aug 4, 2026 •

edited

Loading

Uh oh!

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

edited by datadog-prod-us1-5 Bot

Loading

Uh oh!

pr-commenter Bot commented Aug 4, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Explanation

More details about the CI and significant changes

Uh oh!

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

edited

Loading

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

vpellan left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Uh oh!

Conversation

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

Uh oh!

What does this PR do?

Motivation

Additional Notes

How to test the change?

Uh oh!

datadog-datadog-prod-us1 Bot commented Aug 4, 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!

pr-commenter Bot commented Aug 4, 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:credit_card/is_card_number/x371413321323331

scenario:credit_card/is_card_number_no_luhn/x371413321323331

scenario:otlp/e2e_json/1x1000

scenario:otlp/encode_json/1x1000

scenario:vec_map/dedup/dup_1_in_10/16

scenario:vec_map/get_hit/128

scenario:vec_map/get_hit/16

scenario:vec_map/get_hit/64

scenario:vec_map/get_hit/8

scenario:vec_map/iter/128

scenario:vec_map/iter/8

Explanation

More details about the CI and significant changes

scenario:datadog_sample_span/complex_rule_matching/wall_time

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

scenario:glob_matcher/ascii_exact_match/wall_time

scenario:glob_matcher/ascii_exact_miss/wall_time

scenario:glob_matcher/unicode_exact_match/wall_time

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

scenario:trace_buffer/4_senders/no_delay

scenario:trace_buffer/8_senders/no_delay

Candidate

Baseline

Uh oh!

dd-octo-sts Bot commented Aug 4, 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!

vpellan left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

mabdinur commented Aug 4, 2026 •

edited

Loading

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

edited by datadog-prod-us1-5 Bot

Loading

pr-commenter Bot commented Aug 4, 2026 •

edited

Loading

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

edited

Loading