feat(trace-utils): add _dd.sdk.otlp_export and datadog.sdk.semantics OTLP resource attributes by mhlidd · Pull Request #2603 · DataDog/libdatadog

mhlidd · 2026-09-30T19:08:38Z

What does this PR do?

Adds two OTLP resource attributes to traces exported over OTLP, and strips a conflicting span-level marker:

_dd.sdk.otlp_export: "true" — always set in build_resource, since reaching the OTLP encoder means the payload is leaving over OTLP.
datadog.sdk.semantics — "otel" when OTel trace semantics mode is enabled (TraceExporterBuilder::enable_otel_trace_semantics()), "datadog" otherwise.
Any span-level _dd.sdk.otlp_export (tracers stamp "false" on native payloads; users can set it via DD_TAGS) is dropped from OTLP span attributes in both the v0.4 mapper (meta loop, with dropped-count accounting kept in sync) and the v1 mapper (is_eligible), so it can never contradict the resource value.

The semantics flag is threaded into build_resource as a parameter (it is pub(super)) rather than added to OtlpResourceInfo: both map_traces_to_otlp* entry points already receive it per call, so a struct field would duplicate state that could diverge. No public API change.

Motivation

RFC: Measuring Adoption of Datadog SDKs in OTel Mode (Traces). The intake cannot currently tell a Datadog SDK exporting over OTLP apart from a native payload converted to OTLP by the Collector's datadogreceiver (both set a Datadog-owned telemetry.sdk.name). SDKs now declare the export mode explicitly; the backend promotes the marker to datadog.sdk.otlp_export on dd.trace.intake.ingested_spans, and datadog.sdk.semantics lets us measure OTel-semantics adoption.

Equivalent Java change: DataDog/dd-trace-java#12516 (OtlpResourceAttributes). SDKs that export OTLP through libdatadog (e.g. dd-trace-py) get this without language-side changes beyond a version bump.

Additional Notes

Companion dd-trace-py change (native-path _dd.sdk.otlp_export:false): chore(tracing): mark native trace export with _dd.sdk.otlp_export dd-trace-py#20703. dd-trace-py already calls enable_otel_trace_semantics() when semantics mode + OTLP are on, so it only needs a libdatadog pin bump after this is released.
libdd-data-pipeline-ffi does not expose enable_otel_trace_semantics, so FFI consumers will always report datadog.sdk.semantics: "datadog" until a setter is added (out of scope here).
The OTLP metrics resource (libdd-data-pipeline/src/otlp/metrics.rs) is unchanged; the RFC covers traces only.

How to test the change?

Unit tests (libdd-trace-utils/src/otlp_encoder/mapper.rs, mapper_v1.rs): resource carries both attributes for each flag value; span meta _dd.sdk.otlp_export is stripped and the dropped count stays correct past the attribute cap. v1 also has a chunk-only case (marker only in chunk.attributes, past the cap), since a span-level copy would win the merge and hide the chunk path.
Integration tests updated for the new resource attributes: test_trace_exporter_otlp_export.rs (semantics on → "otel"), test_trace_exporter_otlp_grpc.rs, test_trace_exporter_otlp_protobuf_export.rs (→ "datadog").

Run locally:

cargo test -p libdd-trace-utils otlp — 62 passed; --lib 466 passed
cargo test -p libdd-data-pipeline --test test_trace_exporter_otlp_export --test test_trace_exporter_otlp_grpc --test test_trace_exporter_otlp_protobuf_export — 7 passed
cargo clippy -p libdd-trace-utils -p libdd-data-pipeline --all-targets -- -D warnings — clean
cargo fmt --all -- --check — clean (run on stable cargo, not the pinned nightly; CI fmt will confirm)
cargo test -p libdd-data-pipeline --lib — 200 passed, 2 failed (test_agent_info_fetcher_run, test_v1_404_fails_closed_to_v04); both pass in isolation — they are single_threaded_tests intended for nextest, unrelated to this change.

🤖 Generated with Claude Code

…OTLP resource attributes Mark OTLP trace payloads so the intake can tell a Datadog SDK exporting over OTLP apart from a native payload converted by the datadogreceiver (RFC: Measuring Adoption of Datadog SDKs in OTel Mode). The resource now carries _dd.sdk.otlp_export:true and datadog.sdk.semantics ("otel" when OTel trace semantics is enabled, else "datadog"). Any span-level _dd.sdk.otlp_export is stripped from span attributes (v0.4 and v1 mappers) so it cannot contradict the resource value. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

datadog-prod-us1-5 · 2026-09-30T19:19:25Z

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 98.84%
• Overall Coverage: 80.05% (+0.04%)

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

🔗 Commit SHA: 321fe20 | Docs | View more details | Give us feedback!}

pr-commenter · 2026-09-30T19:38:18Z

Benchmarks

Comparison

Benchmark execution time: 2026-09-30 20:40:24

Comparing candidate commit 321fe20 in PR branch matthew.li/sdk-otlp-export-marker with baseline commit 264a929 in branch main.

📊 Benchmarking dashboard

Found 7 performance improvements and 2 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:msgpack_decoder::v05/low_sharing/10000

🟩 execution_time [-742.564µs; -734.402µs] or [-4.133%; -4.087%]
🟩 throughput [+23722.562op/s; +23990.970op/s] or [+4.262%; +4.311%]

scenario:msgpack_decoder::v05/low_sharing/2000

🟩 execution_time [-153.670µs; -151.835µs] or [-4.224%; -4.174%]
🟩 throughput [+23955.807op/s; +24240.272op/s] or [+4.357%; +4.409%]

scenario:otlp/e2e_json/1x1000

🟩 execution_time [-407.181µs; -397.304µs] or [-9.181%; -8.958%]

scenario:otlp/encode_json/1x1000

🟩 execution_time [-375.475µs; -372.132µs] or [-18.424%; -18.260%]

scenario:otlp/encode_protobuf/1x1000

🟥 execution_time [+58.446µs; +58.859µs] or [+5.616%; +5.655%]

scenario:vec_map/as_deduped_map/already_deduped/16

🟥 execution_time [+7.418ns; +7.441ns] or [+31.479%; +31.580%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_10/8

🟩 execution_time [-17.312ns; -17.098ns] or [-4.658%; -4.600%]

Benchmark execution time: 2026-09-30 20:40:12

Comparing candidate commit 321fe20 in PR branch matthew.li/sdk-otlp-export-marker with baseline commit 264a929 in branch main.

📊 Benchmarking dashboard

Found 0 performance improvements and 6 performance regressions! Performance is the same for 102 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_partial_match/wall_time

🟥 execution_time [+10.706ns; +10.828ns] or [+4.569%; +4.621%]

scenario:datadog_sample_span/tag_rule_matching/wall_time

🟥 execution_time [+14.066ns; +14.196ns] or [+4.195%; +4.234%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

🟥 execution_time [+4.481ns; +4.500ns] or [+12.026%; +12.078%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/wall_time

🟥 execution_time [+4.810ns; +4.835ns] or [+11.767%; +11.827%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

🟥 execution_time [+4.794ns; +4.812ns] or [+13.018%; +13.067%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

🟥 execution_time [+4.793ns; +4.809ns] or [+13.019%; +13.063%]

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:datadog_sample_span/parent_not_sampled_short_circuit/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+558.060%; -556.831%]

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+556.122%; -555.917%]

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+555.735%; -555.735%]

scenario:glob_matcher/ascii_exact_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+555.169%; -555.469%]

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+569.985%; -562.493%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+554.961%; -555.370%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+555.735%; -555.735%]

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+556.503%; -556.096%]

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+555.735%; -555.735%]

scenario:glob_matcher/star_short_circuit/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+555.927%; -555.825%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

dd-octo-sts · 2026-09-30T19:44:41Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	9.08 MB	9.08 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	96.53 MB	96.53 MB	-0% (-288 B) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.27 MB	12.27 MB	+0% (+48 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	107.92 MB	107.92 MB	-0% (-536 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	29.13 MB	29.13 MB	+0% (+512 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	97.94 KB	97.94 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	191.87 MB	191.87 MB	+0% (+8.00 KB) 👌
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	820.58 MB	821.98 MB	+.17% (+1.40 MB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	9.75 MB	9.76 MB	+.05% (+5.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	97.94 KB	97.94 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	27.60 MB	27.60 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	55.79 MB	55.80 MB	+.01% (+7.20 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	25.47 MB	25.47 MB	-0% (-512 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	99.47 KB	99.47 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	197.18 MB	197.15 MB	--.01% (-32.00 KB) 💪
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	803.79 MB	802.65 MB	--.14% (-1.14 MB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	7.57 MB	7.57 MB	+.01% (+1.50 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	99.47 KB	99.47 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	29.72 MB	29.72 MB	0% (0 B) 👌
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	52.72 MB	52.72 MB	+0% (+2.97 KB) 👌

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	86.49 MB	86.50 MB	+0% (+4.44 KB) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	10.10 MB	10.10 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	102.34 MB	102.35 MB	+0% (+4.81 KB) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.35 MB	12.35 MB	0% (0 B) 👌

Copilot

Copilot review overview

🟡 Changes recommended

The v1 test does not actually exercise chunk-only marker filtering because the duplicate span attribute suppresses it first.

Review effort: Balanced
Findings: 1

Open (1)

Add test covering chunk-only marker filtering and dropped-count accounting · New

What changed in this PR

Adds OTLP resource attributes identifying Datadog SDK exports and trace semantics while removing conflicting span-level markers.

Changes:

Adds _dd.sdk.otlp_export and datadog.sdk.semantics resource attributes.
Strips span-level export markers in v0.4 and v1 mappings.
Updates unit and integration coverage across OTLP transports.

File	Description
`libdd-trace-utils/src/otlp_encoder/mapper.rs`	Adds resource markers and v0.4 filtering.
`libdd-trace-utils/src/otlp_encoder/mapper_v1.rs`	Adds v1 resource markers and filtering.
`libdd-data-pipeline/src/trace_exporter/builder.rs`	Documents semantics behavior.
`libdd-data-pipeline/tests/test_trace_exporter_otlp_export.rs`	Verifies JSON OTLP attributes.
`libdd-data-pipeline/tests/test_trace_exporter_otlp_grpc.rs`	Verifies gRPC resource attributes.
`libdd-data-pipeline/tests/test_trace_exporter_otlp_protobuf_export.rs`	Verifies protobuf resource attributes.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bf2ab9908d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

…v1 mapper The existing test put the marker on both the span and the chunk, so merged_attrs_v1 discarded the chunk copy as a collision before the eligibility filter ran. Add a case where only the chunk carries the marker, past the attribute cap, asserting it is stripped and not counted as dropped. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

…ibdd-data-pipeline, libdd-li... (#2619)  # Release proposal for libdd-capabilities-impl, libdd-common, libdd-data-pipeline, libdd-library-config, libdd-profiling-heap-allocator, libdd-remote-config, libdd-sampling, libdd-shared-runtime, libdd-telemetry, libdd-tinybytes, libdd-trace-utils and their dependencies This PR contains version bumps based on public API changes and commits since last release. ### ⚠️ Crates left out of this proposal affected by its major bumps These publishable workspace crates are not part of this release but their dependency requirement was rewritten on this branch while their published version still requires the old major. If they are a dependency on your deployment not including them in the release could result in duplicate packages or symbol incompatibility. - `libdd-capabilities-impl` `6.0.0` → `7.0.0` affects: `libdd-crashtracker`, `libdd-live-debugger`, `libdd-tracer-flare` - `libdd-common` `7.0.0` → `8.0.0` affects: `libdd-crashtracker`, `libdd-ffe`, `libdd-http-client`, `libdd-ipc`, `libdd-live-debugger`, `libdd-profiling`, `libdd-tracer-flare` - `libdd-data-pipeline` `11.0.0` → `12.0.0` affects: `libdd-live-debugger` - `libdd-remote-config` `6.0.0` → `7.0.0` affects: `libdd-ffe`, `libdd-live-debugger`, `libdd-tracer-flare` - `libdd-telemetry` `9.0.0` → `10.0.0` affects: `libdd-crashtracker` - `libdd-trace-stats` `10.0.0` → `11.0.0` affects: `libdd-ipc` - `libdd-trace-utils` `13.0.0` → `14.0.0` affects: `libdd-tracer-flare` ## libdd-capabilities **Next version:** `4.0.1` **Semver bump:** `patch` **Tag:** `libdd-capabilities-v4.0.1` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-common **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-common-v8.0.0` ### Commits - fix(ipc)!: use atomic deadlines for shared limiters (#2604) - feat(sidecar)!: Authenticate sidecar connections and shared memory (#2551) - build: Update workspace to Rust 2024 edition (#2575) - feat(trace_utils)!: add mutable metadata (#2545) ## libdd-ddsketch **Next version:** `1.1.3` **Semver bump:** `patch` **Tag:** `libdd-ddsketch-v1.1.3` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-profiling-heap-sampler **Next version:** `1.1.1` **Semver bump:** `patch` **Tag:** `libdd-profiling-heap-sampler-v1.1.1` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-tinybytes **Next version:** `1.1.5` **Semver bump:** `patch` **Tag:** `libdd-tinybytes-v1.1.5` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-trace-protobuf **Next version:** `5.1.0` **Semver bump:** `minor` **Tag:** `libdd-trace-protobuf-v5.1.0` ### Commits - fix(data-pipeline)!: revert changes that made /info un-parsable (#2586) - build: Update workspace to Rust 2024 edition (#2575) ## libdd-capabilities-impl **Next version:** `7.0.0` **Semver bump:** `major` **Tag:** `libdd-capabilities-impl-v7.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - feat(sidecar)!: Authenticate sidecar connections and shared memory (#2551) - build: Update workspace to Rust 2024 edition (#2575) ## libdd-profiling-heap-allocator **Next version:** `1.2.0` **Semver bump:** `minor` **Tag:** `libdd-profiling-heap-allocator-v1.2.0` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-library-config **Next version:** `4.2.0` **Semver bump:** `minor` **Tag:** `libdd-library-config-v4.2.0` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-trace-normalization **Next version:** `4.2.0` **Semver bump:** `minor` **Tag:** `libdd-trace-normalization-v4.2.0` ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-remote-config **Next version:** `7.0.0` **Semver bump:** `major` **Tag:** `libdd-remote-config-v7.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - feat(sidecar)!: Authenticate sidecar connections and shared memory (#2551) - build: Update workspace to Rust 2024 edition (#2575) ## libdd-shared-runtime **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-shared-runtime-v6.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-trace-utils **Next version:** `14.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-utils-v14.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - feat(trace-utils): add _dd.sdk.otlp_export and datadog.sdk.semantics OTLP resource attributes (#2603) - build: Update workspace to Rust 2024 edition (#2575) - feat(trace_utils)!: add mutable metadata (#2545) ## libdd-dogstatsd-client **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-dogstatsd-client-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - feat(sidecar)!: Authenticate sidecar connections and shared memory (#2551) - build: Update workspace to Rust 2024 edition (#2575) ## libdd-telemetry **Next version:** `10.0.0` **Semver bump:** `major` **Tag:** `libdd-telemetry-v10.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 ### Commits - build: Update workspace to Rust 2024 edition (#2575) - feat(telemetry)!: Use mutable metadata (#2552) ## libdd-sampling **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-sampling-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 - `libdd-trace-utils`: ^13.0.0 → ^14.0.0 ### Commits - build: Update workspace to Rust 2024 edition (#2575) ## libdd-trace-obfuscation **Next version:** `10.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-obfuscation-v10.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 - `libdd-trace-utils`: ^13.0.0 → ^14.0.0 ### Commits - fix(data-pipeline)!: revert changes that made /info un-parsable (#2586) - build: Update workspace to Rust 2024 edition (#2575) - feat(obfuscation)!: make json transforms caller-provided (#2548) ## libdd-trace-stats **Next version:** `11.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-stats-v11.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 - `libdd-telemetry`: ^9.0.0 → ^10.0.0 - `libdd-trace-obfuscation`: ^9.0.0 → ^10.0.0 - `libdd-trace-utils`: ^13.0.0 → ^14.0.0 ### Commits - feat(sidecar)!: Authenticate sidecar connections and shared memory (#2551) - build: Update workspace to Rust 2024 edition (#2575) - feat(trace_utils)!: add mutable metadata (#2545) - fix(stats): fix precedence for http endpoint (#2582) ## libdd-data-pipeline-core **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-core-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 - `libdd-trace-obfuscation`: ^9.0.0 → ^10.0.0 - `libdd-trace-stats`: ^10.0.0 → ^11.0.0 - `libdd-trace-utils`: ^13.0.0 → ^14.0.0 ### Commits - build: Update workspace to Rust 2024 edition (#2575) - feat(trace_utils)!: add mutable metadata (#2545) ## libdd-data-pipeline **Next version:** `12.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-v12.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^7.0.0 → ^8.0.0 - `libdd-telemetry`: ^9.0.0 → ^10.0.0 - `libdd-trace-obfuscation`: ^9.0.0 → ^10.0.0 - `libdd-trace-stats`: ^10.0.0 → ^11.0.0 - `libdd-trace-utils`: ^13.0.0 → ^14.0.0 ### Commits - feat(trace-utils): add _dd.sdk.otlp_export and datadog.sdk.semantics OTLP resource attributes (#2603) - fix(data-pipeline)!: revert changes that made /info un-parsable (#2586) - build: Update workspace to Rust 2024 edition (#2575) - feat(telemetry)!: Use mutable metadata (#2552) - feat(trace_utils)!: add mutable metadata (#2545) --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: iunanua <18325288+iunanua@users.noreply.github.com>

mhlidd added the AI Generated PR largely written by AI tools label Sep 30, 2026

github-actions Bot added mini-agent data-pipeline labels Sep 30, 2026

mhlidd marked this pull request as ready for review September 30, 2026 19:59

mhlidd requested review from a team as code owners September 30, 2026 19:59

mhlidd requested review from vpellan and a balanced review from Copilot and removed request for a team September 30, 2026 19:59

Copilot started reviewing on behalf of mhlidd September 30, 2026 19:59 View session

Copilot AI reviewed Sep 30, 2026

View reviewed changes

Comment thread libdd-trace-utils/src/otlp_encoder/mapper_v1.rs

chatgpt-codex-connector Bot reviewed Sep 30, 2026

View reviewed changes

Comment thread libdd-trace-utils/src/otlp_encoder/mapper.rs

yannham approved these changes Oct 1, 2026

View reviewed changes

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

gh-worker-dd-mergequeue-cf854d Bot merged commit ab1c67a into main Oct 1, 2026
115 of 121 checks passed

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

gh-worker-dd-mergequeue-cf854d Bot deleted the matthew.li/sdk-otlp-export-marker branch October 1, 2026 18:44

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

dd-octo-sts Bot mentioned this pull request Oct 2, 2026

chore(release): proposal for libdd-capabilities-impl, libdd-common, libdd-data-pipeline, libdd-li... #2619

Merged

Conversation

mhlidd commented Sep 30, 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-prod-us1-5 Bot commented Sep 30, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pr-commenter Bot commented Sep 30, 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/low_sharing/10000

scenario:msgpack_decoder::v05/low_sharing/2000

scenario:otlp/e2e_json/1x1000

scenario:otlp/encode_json/1x1000

scenario:otlp/encode_protobuf/1x1000

scenario:vec_map/as_deduped_map/already_deduped/16

scenario:vec_map/as_deduped_map/needs_dedup_1_in_10/8

Explanation

More details about the CI and significant changes

scenario:datadog_sample_span/complex_rule_partial_match/wall_time

scenario:datadog_sample_span/tag_rule_matching/wall_time

scenario:glob_matcher/ascii_wildcard_backtrack_match/wall_time

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/wall_time

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

Unstable benchmarks

scenario:datadog_sample_span/parent_not_sampled_short_circuit/allocated_bytes

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

scenario:glob_matcher/ascii_exact_match/allocated_bytes

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

scenario:glob_matcher/star_short_circuit/allocated_bytes

Candidate

Baseline

Uh oh!

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

Uh oh!

Artifact Size Benchmark Report

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Copilot review overview

🟡 Changes recommended

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

mhlidd commented Sep 30, 2026 •

edited

Loading

datadog-prod-us1-5 Bot commented Sep 30, 2026 •

edited

Loading

pr-commenter Bot commented Sep 30, 2026 •

edited

Loading

dd-octo-sts Bot commented Sep 30, 2026 •

edited

Loading