feat(trace_utils)!: add mutable metadata by VianneyRuhlmann · Pull Request #2545 · DataDog/libdatadog

VianneyRuhlmann · 2026-09-17T16:43:16Z

What does this PR do?

Introduce a shared structure for mutable metadata. All the components hold a MutableMetadataHandle which stores an ArcSwap of the mutable fields. The SDK can update these values and the components must load the new value whenever they access them.

Motivation

Allow runtime_id to be updated without recreating components. Other values will benefit from this feature e.g. process_tags, test_session_token.

Breaking change

What changed

Struct	Removed fields	New field
`TracerMetadata`	`runtime_id`, `process_tags`	`mutable_metadata: MutableMetadataHandle`
`StatsMetadata`	`runtime_id`, `process_tags`	`mutable_metadata: MutableMetadataHandle`
`OtlpResourceInfo`	`runtime_id`, `process_tags`	`mutable_metadata: MutableMetadataHandle`

Formats are unchanged: runtime_id is a runtime UUID; process_tags is a
comma-separated key:value string.

Migrating construction

Replace the two removed fields with one MutableMetadataHandle. Initialize it from
a MutableMetadata snapshot:

// Before
let metadata = TracerMetadata {
    runtime_id: rt_id,
    process_tags: tags,
    ..Default::default()
};

// After
let mut snapshot = MutableMetadata::default();
snapshot.runtime_id = rt_id;
snapshot.process_tags = tags;
let metadata = TracerMetadata {
    mutable_metadata: MutableMetadataHandle::from(snapshot),
    ..Default::default()
};

Migrating field reads

Values are no longer stored on the struct; read a snapshot through the handle at the
point of use:

// Before
let rt = metadata.runtime_id;
let tags = &metadata.process_tags;

// After
let snapshot = metadata.mutable_metadata.load();
let rt = &snapshot.runtime_id;
let tags = &snapshot.process_tags;

APMSP-3368 [APMSP-3369]

dd-octo-sts · 2026-09-17T17:18:54Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	96.05 MB	96.24 MB	+.19% (+187.45 KB) 🔍
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	9.02 MB	9.08 MB	+.69% (+64.09 KB) 🔍

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.19 MB	12.20 MB	+.05% (+7.36 KB) 🔍
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	107.43 MB	107.62 MB	+.17% (+197.82 KB) 🔍

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	29.08 MB	29.13 MB	+.17% (+52.00 KB) 🔍
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	96.08 KB	97.60 KB	+1.58% (+1.52 KB) ⚠️
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	191.51 MB	191.91 MB	+.20% (+400.00 KB) 🔍
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	815.49 MB	817.94 MB	+.30% (+2.45 MB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	9.72 MB	9.74 MB	+.21% (+21.00 KB) 🔍
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	96.08 KB	97.60 KB	+1.58% (+1.52 KB) ⚠️
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	27.51 MB	27.57 MB	+.19% (+56.00 KB) 🔍
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	55.62 MB	55.74 MB	+.21% (+123.59 KB) 🔍

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	25.42 MB	25.47 MB	+.18% (+47.00 KB) 🔍
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	97.58 KB	99.13 KB	+1.58% (+1.54 KB) ⚠️
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	196.76 MB	197.15 MB	+.19% (+392.00 KB) 🔍
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	802.14 MB	804.90 MB	+.34% (+2.75 MB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	7.54 MB	7.56 MB	+.17% (+13.50 KB) 🔍
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	97.58 KB	99.13 KB	+1.58% (+1.54 KB) ⚠️
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	29.62 MB	29.69 MB	+.23% (+72.00 KB) 🔍
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	52.56 MB	52.67 MB	+.20% (+112.91 KB) 🔍

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	86.06 MB	86.23 MB	+.20% (+177.06 KB) 🔍
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	10.06 MB	10.07 MB	+.11% (+12.09 KB) 🔍

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	101.90 MB	102.08 MB	+.17% (+184.02 KB) 🔍
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	12.28 MB	12.31 MB	+.23% (+30.12 KB) 🔍

pr-commenter · 2026-09-17T17:31:32Z

Benchmarks

Comparison

Benchmark execution time: 2026-09-28 14:11:22

Comparing candidate commit 9e5579d in PR branch vianney/mutable-runtime-id with baseline commit 679f332 in branch main.

📊 Benchmarking dashboard

Found 7 performance improvements and 8 performance regressions! Performance is the same for 162 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:agentless_encoding/common_http/20x5

🟩 execution_time [-14.806µs; -14.753µs] or [-12.708%; -12.662%]
🟩 throughput [+124454.406op/s; +124918.543op/s] or [+14.501%; +14.555%]

scenario:agentless_encoding/http_with_span_links/20x5

🟩 execution_time [-15.731µs; -15.598µs] or [-11.894%; -11.794%]
🟩 throughput [+101184.520op/s; +101964.687op/s] or [+13.382%; +13.486%]

scenario:vec_map/as_deduped_map/already_deduped/16

🟩 execution_time [-1.216ns; -1.200ns] or [-4.799%; -4.734%]

scenario:vec_map/as_deduped_map/already_deduped/8

🟩 execution_time [-1.215ns; -1.204ns] or [-7.745%; -7.677%]

scenario:vec_map/dedup/dup_1_in_4/8

🟩 execution_time [-23.970ns; -20.414ns] or [-5.071%; -4.319%]

scenario:vec_map/get_hit/128

🟥 execution_time [+1.267µs; +1.274µs] or [+10.168%; +10.225%]
🟥 throughput [-953419.158op/s; -948025.571op/s] or [-9.279%; -9.227%]

scenario:vec_map/get_hit/16

🟥 execution_time [+22.798ns; +23.041ns] or [+10.731%; +10.845%]
🟥 throughput [-7369775.650op/s; -7295394.104op/s] or [-9.786%; -9.687%]

scenario:vec_map/get_hit/64

🟥 execution_time [+295.514ns; +298.810ns] or [+8.730%; +8.828%]
🟥 throughput [-1534448.891op/s; -1517526.492op/s] or [-8.115%; -8.026%]

scenario:vec_map/get_hit/8

🟥 execution_time [+3.267ns; +3.406ns] or [+5.313%; +5.541%]
🟥 throughput [-6851764.378op/s; -6559970.390op/s] or [-5.265%; -5.041%]

Benchmark execution time: 2026-09-28 14:04:25

Comparing candidate commit 9e5579d in PR branch vianney/mutable-runtime-id with baseline commit 679f332 in branch main.

📊 Benchmarking dashboard

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

🟥 execution_time [+4.978µs; +5.075µs] or [+7.312%; +7.454%]
🟥 throughput [-1018698.473op/s; -1000476.226op/s] or [-6.935%; -6.811%]

scenario:credit_card/is_card_number/378282246310005

🟥 execution_time [+4.990µs; +5.050µs] or [+7.662%; +7.753%]
🟥 throughput [-1104868.012op/s; -1092488.008op/s] or [-7.196%; -7.115%]

scenario:credit_card/is_card_number/37828224631000521389798

🟥 execution_time [+6.159µs; +6.224µs] or [+13.436%; +13.576%]
🟥 throughput [-2611381.561op/s; -2580848.411op/s] or [-11.971%; -11.831%]

scenario:credit_card/is_card_number/x371413321323331

🟩 execution_time [-892.870ns; -873.484ns] or [-13.427%; -13.136%]
🟩 throughput [+22769820.194op/s; +23341527.203op/s] or [+15.141%; +15.522%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

🟥 execution_time [+4.136µs; +4.171µs] or [+7.725%; +7.791%]
🟥 throughput [-1350049.765op/s; -1339192.268op/s] or [-7.228%; -7.170%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

🟥 execution_time [+4.533µs; +4.565µs] or [+9.008%; +9.071%]
🟥 throughput [-1652658.120op/s; -1641689.331op/s] or [-8.317%; -8.262%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

🟥 execution_time [+6.115µs; +6.173µs] or [+13.324%; +13.450%]
🟥 throughput [-2586426.759op/s; -2559316.624op/s] or [-11.870%; -11.745%]

scenario:credit_card/is_card_number_no_luhn/x371413321323331

🟩 execution_time [-903.582ns; -886.223ns] or [-13.591%; -13.330%]
🟩 throughput [+23158268.314op/s; +23669844.921op/s] or [+15.397%; +15.737%]

scenario:flagevaluation_evp/payloads/scale/2500flags_500users_20fields

🟥 execution_time [+1.010ms; +1.033ms] or [+4.755%; +4.865%]
🟥 throughput [-5462.396op/s; -5343.200op/s] or [-4.639%; -4.538%]

scenario:flagevaluation_evp/payloads/stress/10flags_1000users_250fields

🟥 execution_time [+7.229ms; +7.374ms] or [+7.396%; +7.544%]
🟥 throughput [-718.119op/s; -704.186op/s] or [-7.019%; -6.883%]

scenario:glob_matcher/ascii_exact_miss/wall_time

🟩 execution_time [-0.828ns; -0.770ns] or [-5.836%; -5.427%]

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

🟥 execution_time [+3.939ns; +3.996ns] or [+4.338%; +4.401%]

scenario:sql/obfuscate_sql_string

🟩 execution_time [-13.885µs; -13.666µs] or [-4.514%; -4.443%]

scenario:thread_cpu/alloc_free/system/4096

🟥 execution_time [+13.380ns; +13.583ns] or [+14.539%; +14.759%]

scenario:trace_buffer/2_senders/no_delay

🟥 execution_time [+326.550µs; +339.694µs] or [+21.346%; +22.205%]
🟥 throughput [-214801.606op/s; -206323.178op/s] or [-18.248%; -17.528%]

scenario:trace_buffer/4_senders/no_delay

🟥 execution_time [+150.366µs; +158.788µs] or [+4.361%; +4.606%]
🟥 throughput [-46034.784op/s; -43590.245op/s] or [-4.409%; -4.174%]

scenario:trace_buffer/8_senders/no_delay

🟥 execution_time [+268.220µs; +282.891µs] or [+4.195%; +4.424%]
🟥 throughput [-47774.396op/s; -45316.073op/s] or [-4.242%; -4.024%]

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 [+554.966%; -555.373%]

scenario:datadog_sample_span/parent_sampled_short_circuit/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+557.673%; -556.648%]

scenario:glob_matcher/ascii_case_insensitive_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+530.979%; -544.249%]

scenario:glob_matcher/ascii_exact_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+542.162%; -549.395%]

scenario:glob_matcher/ascii_exact_miss/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+550.595%; -553.322%]

scenario:glob_matcher/ascii_wildcard_backtrack_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+564.616%; -559.935%]

scenario:glob_matcher/ascii_wildcard_heavy_backtrack/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+548.872%; -552.517%]

scenario:glob_matcher/ascii_wildcard_question_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+550.284%; -553.177%]

scenario:glob_matcher/ascii_wildcard_star_match/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+550.318%; -553.193%]

scenario:glob_matcher/star_short_circuit/allocated_bytes

unstable execution_time [-0.000ns; +0.000ns] or [+566.193%; -560.685%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

datadog-official · 2026-09-18T09:48:00Z

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 94.46%
• Overall Coverage: 78.62% (+0.01%)

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

🔗 Commit SHA: 9e5579d | Docs | View more details | Give us feedback!}

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9d7f2f9909

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

yannham

I haven't looked at yet, but I wonder how this will interact with metadata publication in libdd_library_config_ffi::tracer_metadata::ddog_tracer_metadata_store (which publishes the metadata to some shared memory, including the OTel process context). Which I think more or less assume that the metadata are immutable once published. Should re-publication be automatic (if that's even possible) upon modification? Or we will ask the tracers to re-publish manually if the want to update?

VianneyRuhlmann · 2026-09-22T13:16:15Z

Currently the runtime_id already changes on a fork. I'm not sure how libdd_library_config_ffi handles it (the tracer probably has to call set_metadata again), but I think these are different concerns. This PR only make it possible to reuse a component when one of these values change without having to recreate the whole component.

yannham

In general I have a vague feeling that we're surfacing internal details to external API...I wonder if we could hide MutableMetadata a bit more, and just offer traditional get/set API externally

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

VianneyRuhlmann force-pushed the vianney/mutable-runtime-id branch from c1b974e to 19885ab Compare September 18, 2026 09:43

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

VianneyRuhlmann added this pull request to stack #2553 September 21, 2026 09:29

github-actions Bot added the common label Sep 21, 2026

VianneyRuhlmann changed the title ~~feat(trace_utils): add mutable metadata~~ feat(trace_utils)!: add mutable metadata Sep 22, 2026

VianneyRuhlmann marked this pull request as ready for review September 22, 2026 10:05

VianneyRuhlmann requested review from a team as code owners September 22, 2026 10:06

VianneyRuhlmann requested review from mabdinur and removed request for a team September 22, 2026 10:06

chatgpt-codex-connector Bot reviewed Sep 22, 2026

View reviewed changes

Comment thread libdd-common-ffi/src/mutable_metadata.rs Outdated

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

yannham reviewed Sep 22, 2026

View reviewed changes

Eldolfin reviewed Sep 24, 2026

View reviewed changes

VianneyRuhlmann force-pushed the vianney/mutable-runtime-id branch from 9d90564 to dc4b783 Compare September 25, 2026 14:04

yannham reviewed Sep 25, 2026

View reviewed changes

Comment thread libdd-common/src/mutable_metadata.rs

Comment thread libdd-data-pipeline-ffi/src/trace_exporter.rs

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

VianneyRuhlmann added 4 commits September 28, 2026 14:30

feat(trace_utils): add mutable metadata

4f48d59

fix test helper

79ef134

move mutable metadata to ddcommon

49a1650

add ffi bindings

3015fa8

VianneyRuhlmann added 3 commits September 28, 2026 14:32

fix lint

8edcf8b

apply suggestions

dafc8ba

update fallback setters

e6be726

VianneyRuhlmann force-pushed the vianney/mutable-runtime-id branch from af2fbfc to e6be726 Compare September 28, 2026 12:41

yannham approved these changes Sep 28, 2026

View reviewed changes

fix clippy

9e5579d

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

gh-worker-dd-mergequeue-cf854d Bot merged commit 823002e into main Sep 29, 2026
103 checks passed

gh-worker-dd-mergequeue-cf854d Bot deleted the vianney/mutable-runtime-id branch September 29, 2026 14:46

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

colin-higgins mentioned this pull request Sep 29, 2026

ci: Introduce ast-grep, rule skill guidance, extern c panic rule #2595

Open

Eldolfin mentioned this pull request Oct 2, 2026

chore(release): proposal for libdd-data-pipeline and its dependencies #2615

Closed

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

VianneyRuhlmann commented Sep 17, 2026 • edited by atlassian Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Motivation

Breaking change

What changed

Migrating construction

Migrating field reads

Uh oh!

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

Uh oh!

Artifact Size Benchmark Report

Uh oh!

pr-commenter Bot commented Sep 17, 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:agentless_encoding/common_http/20x5

scenario:agentless_encoding/http_with_span_links/20x5

scenario:vec_map/as_deduped_map/already_deduped/16

scenario:vec_map/as_deduped_map/already_deduped/8

scenario:vec_map/dedup/dup_1_in_4/8

scenario:vec_map/get_hit/128

scenario:vec_map/get_hit/16

scenario:vec_map/get_hit/64

scenario:vec_map/get_hit/8

Explanation

More details about the CI and significant changes

scenario:credit_card/is_card_number/ 378282246310005

scenario:credit_card/is_card_number/378282246310005

scenario:credit_card/is_card_number/37828224631000521389798

scenario:credit_card/is_card_number/x371413321323331

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

scenario:credit_card/is_card_number_no_luhn/378282246310005

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

scenario:credit_card/is_card_number_no_luhn/x371413321323331

scenario:flagevaluation_evp/payloads/scale/2500flags_500users_20fields

scenario:flagevaluation_evp/payloads/stress/10flags_1000users_250fields

scenario:glob_matcher/ascii_exact_miss/wall_time

scenario:glob_matcher/unicode_pattern_ascii_subject/wall_time

scenario:sql/obfuscate_sql_string

scenario:thread_cpu/alloc_free/system/4096

scenario:trace_buffer/2_senders/no_delay

scenario:trace_buffer/4_senders/no_delay

scenario:trace_buffer/8_senders/no_delay

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!

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

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!

yannham left a comment

Choose a reason for hiding this comment

Uh oh!

VianneyRuhlmann commented Sep 22, 2026

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

VianneyRuhlmann commented Sep 17, 2026 •

edited by atlassian Bot

Loading

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

edited

Loading

pr-commenter Bot commented Sep 17, 2026 •

edited

Loading

datadog-official Bot commented Sep 18, 2026 •

edited by datadog-prod-us1-4 Bot

Loading