Skip to content

feat(trace-utils)!: add encoder v1 to v04 + refactor - #2145

Merged
gh-worker-dd-mergequeue-cf854d[bot] merged 23 commits into
mainfrom
anais/encoder-v1-to-v04-and-refacto-2
Jul 15, 2026
Merged

gh-worker-dd-mergequeue-cf854d[bot] merged 23 commits into
mainfrom
anais/encoder-v1-to-v04-and-refacto-2

Conversation

@anais-raison

@anais-raison anais-raison commented Jun 22, 2026 •

Copy link
Copy Markdown
Contributor

What does this PR do?

Adds a V1 → v0.4 msgpack downgrade encoder so a tracer that emits V1 spans natively can still send traces to an agent that only advertises /v0.4/traces.

Also renames the existing encoder modules/functions so the convention is uniform: parent module = output wire format, file/function suffix = input span type. The four combinations now coexist:

  • v04/span_v04.rs — v0.4 → v0.4 (native)
  • v04/span_v1.rs — v1 → v0.4 (downgrade, new)
  • v1/span_v04.rs — v0.4 → V1 (upgrade)
  • v1/span_v1.rs — v1 → V1 (native)

Motivation

APMSP-2811

@datadog-prod-us1-5

datadog-prod-us1-5 Bot commented Jun 22, 2026 •

Copy link
Copy Markdown

Tests

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 91.25%
• Overall Coverage: 74.74% (+0.27%)

This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cbca66a | Docs | Datadog PR Page | Give us feedback!

@dd-octo-sts

dd-octo-sts Bot commented Jun 22, 2026 •

Copy link
Copy Markdown
Contributor

Artifact Size Benchmark Report

aarch64-alpine-linux-musl
Artifact Baseline Commit Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so 7.88 MB 7.88 MB 0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a 86.32 MB 86.32 MB +0% (+6.54 KB) 👌
aarch64-unknown-linux-gnu
Artifact Baseline Commit Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a 97.54 MB 97.54 MB +0% (+128 B) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.62 MB 10.62 MB -0% (-432 B) 👌
libdatadog-x64-windows
Artifact Baseline Commit Change
libdatadog-x86-windows
Artifact Baseline Commit Change
x86_64-alpine-linux-musl
Artifact Baseline Commit Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a 77.09 MB 77.07 MB --.01% (-13.84 KB) 💪
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so 8.83 MB 8.83 MB --.04% (-4.00 KB) 💪
x86_64-unknown-linux-gnu
Artifact Baseline Commit Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a 92.50 MB 92.50 MB -0% (-288 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so 10.74 MB 10.74 MB -0% (-216 B) 👌

@yannham yannham left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM overall 👍 I think the naming convention brings more clarity indeed.

Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
@anais-raison
anais-raison marked this pull request as ready for review June 29, 2026 17:27
@anais-raison
anais-raison requested review from a team as code owners June 29, 2026 17:27

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5fbf20172c

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

Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs
@anais-raison anais-raison changed the title feat: encoder v1 to v04 + refacto feat(trace-utils)!: add encoder v1 to v04 + refactor Jun 29, 2026

@ajgajg1134 ajgajg1134 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some of the function names are confusing me a bit / don't match the comments?
Also I think some of the v1 attribute types need to be "un-done" differently, specifically key values and lists shouldn't just get put in meta_struct and should be flattened into individual meta/metrics entries.

Once you have that changed, we should validate this with some integration tests against the real agent / intake to make sure the payloads match the agent decode and appear correctly in the UI

Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v1/mod.rs Outdated

@Aaalibaba42 Aaalibaba42 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly nits and/or styling, most of these can be disregarded

Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs
Comment thread libdd-trace-utils/src/msgpack_encoder/v1/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v1/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated

@ajgajg1134 ajgajg1134 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes look good! The new names are much clearer to me. I do think we need a better integration / system testing story here though, the unit tests do a good job asserting what we think is right here but alignment with the actual trace-agent is harder to be sure of here. Unless that testing step would happen as part of testing actual integration with something like the rust tracer?

@Aaalibaba42 Aaalibaba42 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For many of the "perf" comments, I didn't look into everything, but I've only really looked at the v04/span_v1.rs encoder, I wager there is more in other parts of the code, maybe try and have an agent scoure for similar issues. We really ought to be mindful of allocations in hotpath, and std structures like HashMaps, HashSets, Vecs, Strings, etc are heap allocated.

Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-data-pipeline/src/trace_exporter/builder.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/mod.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs
Comment thread libdd-trace-utils/src/msgpack_encoder/v04/span_v1.rs Outdated
@pr-commenter

pr-commenter Bot commented Jul 13, 2026 •

Copy link
Copy Markdown

Benchmarks

Comparison

Benchmark execution time: 2026-07-15 13:21:34

Comparing candidate commit cbca66a in PR branch anais/encoder-v1-to-v04-and-refacto-2 with baseline commit a10f667 in branch main.

Found 21 performance improvements and 12 performance regressions! Performance is the same for 109 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:normalization/normalize_name/normalize_name/good

  • 🟩 execution_time [-573.098ns; -504.077ns] or [-5.025%; -4.420%]
  • 🟩 throughput [+4106915.604op/s; +4669504.734op/s] or [+4.683%; +5.325%]

scenario:profiles_dictionary/profile_string_inserts/threads/1

  • 🟥 execution_time [+15.318µs; +18.143µs] or [+5.042%; +5.972%]
  • 🟥 throughput [-191342.450op/s; -160675.433op/s] or [-5.677%; -4.767%]

scenario:vec_map/contains_key/128

  • 🟥 execution_time [+858.253ns; +867.563ns] or [+5.757%; +5.819%]
  • 🟥 throughput [-472179.700op/s; -467216.811op/s] or [-5.500%; -5.442%]

scenario:vec_map/contains_key/16

  • 🟥 execution_time [+23.402ns; +23.731ns] or [+10.132%; +10.275%]
  • 🟥 throughput [-6460248.978op/s; -6368673.592op/s] or [-9.325%; -9.193%]

scenario:vec_map/contains_key/64

  • 🟥 execution_time [+223.067ns; +226.424ns] or [+5.567%; +5.651%]
  • 🟥 throughput [-854393.180op/s; -841951.100op/s] or [-5.349%; -5.272%]

scenario:vec_map/contains_key/8

  • 🟥 execution_time [+3.548ns; +3.643ns] or [+5.005%; +5.137%]
  • 🟥 throughput [-5520110.626op/s; -5373289.953op/s] or [-4.892%; -4.762%]

scenario:vec_map/dedup/dup_1_in_10/8

  • 🟩 execution_time [-29.985ns; -23.504ns] or [-7.233%; -5.670%]

scenario:vec_map/dedup/dup_1_in_4/8

  • 🟩 execution_time [-24.264ns; -20.569ns] or [-5.121%; -4.341%]

scenario:vec_map/dedup/no_duplicates/8

  • 🟩 execution_time [-22.185ns; -17.703ns] or [-6.033%; -4.815%]

scenario:vec_map/get_hit/128

  • 🟩 execution_time [-1.272µs; -1.265µs] or [-9.250%; -9.197%]
  • 🟩 throughput [+943225.493op/s; +948622.830op/s] or [+10.132%; +10.190%]

scenario:vec_map/get_hit/16

  • 🟩 execution_time [-22.727ns; -22.441ns] or [-9.640%; -9.519%]
  • 🟩 throughput [+7145201.133op/s; +7233602.808op/s] or [+10.528%; +10.659%]

scenario:vec_map/get_hit/64

  • 🟩 execution_time [-307.085ns; -302.101ns] or [-8.280%; -8.146%]
  • 🟩 throughput [+1531291.893op/s; +1557399.831op/s] or [+8.873%; +9.025%]

scenario:vec_map/get_hit/8

  • 🟩 execution_time [-3.655ns; -3.542ns] or [-5.636%; -5.462%]
  • 🟩 throughput [+7132514.945op/s; +7369843.871op/s] or [+5.782%; +5.975%]

scenario:vec_map/get_miss/16

  • 🟥 execution_time [+0.843ns; +0.901ns] or [+8.833%; +9.442%]

scenario:vec_map/get_miss/8

  • 🟥 execution_time [+0.281ns; +0.329ns] or [+4.958%; +5.817%]

scenario:vec_map/insert/128

  • 🟩 execution_time [-1.167µs; -1.154µs] or [-31.745%; -31.372%]
  • 🟩 throughput [+15967082.128op/s; +16132433.533op/s] or [+45.867%; +46.342%]

scenario:vec_map/insert/16

  • 🟩 execution_time [-140.075ns; -137.195ns] or [-24.430%; -23.928%]
  • 🟩 throughput [+8804831.799op/s; +9010694.114op/s] or [+31.549%; +32.286%]

scenario:vec_map/insert/64

  • 🟩 execution_time [-589.042ns; -585.244ns] or [-30.956%; -30.757%]
  • 🟩 throughput [+14959856.828op/s; +15061469.807op/s] or [+44.477%; +44.779%]

scenario:vec_map/insert/8

  • 🟩 execution_time [-73.044ns; -72.219ns] or [-24.812%; -24.531%]
  • 🟩 throughput [+8847201.338op/s; +8957200.079op/s] or [+32.555%; +32.960%]

Benchmark execution time: 2026-07-15 13:36:43

Comparing candidate commit cbca66a in PR branch anais/encoder-v1-to-v04-and-refacto-2 with baseline commit a10f667 in branch main.

Found 12 performance improvements and 10 performance regressions! Performance is the same for 155 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:alloc_free/sampled_system_fast_path/256

  • 🟩 execution_time [-1.739ns; -1.632ns] or [-6.302%; -5.912%]

scenario:alloc_free/sampled_system_fast_path/4096

  • 🟩 execution_time [-4.422ns; -4.265ns] or [-4.435%; -4.278%]

scenario:alloc_free/system/4096

  • 🟥 execution_time [+9.103ns; +9.264ns] or [+10.643%; +10.831%]

scenario:credit_card/is_card_number/ 3782-8224-6310-005

  • 🟩 execution_time [-4.935µs; -4.757µs] or [-6.173%; -5.950%]
  • 🟩 throughput [+792324.158op/s; +822688.271op/s] or [+6.334%; +6.577%]

scenario:credit_card/is_card_number/ 378282246310005

  • 🟥 execution_time [+7.634µs; +7.739µs] or [+10.435%; +10.578%]
  • 🟥 throughput [-1309461.568op/s; -1290343.947op/s] or [-9.580%; -9.440%]

scenario:credit_card/is_card_number/378282246310005

  • 🟩 execution_time [-5.395µs; -5.297µs] or [-7.717%; -7.577%]
  • 🟩 throughput [+1173887.301op/s; +1194001.205op/s] or [+8.207%; +8.348%]

scenario:credit_card/is_card_number/37828224631000521389798

  • 🟩 execution_time [-7.013µs; -6.969µs] or [-13.414%; -13.331%]
  • 🟩 throughput [+2942655.347op/s; +2963594.642op/s] or [+15.383%; +15.493%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

  • 🟩 execution_time [-5.589µs; -5.532µs] or [-9.529%; -9.433%]
  • 🟩 throughput [+1777426.439op/s; +1794065.446op/s] or [+10.424%; +10.521%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

  • 🟥 execution_time [+4.018µs; +4.075µs] or [+7.242%; +7.345%]
  • 🟥 throughput [-1234600.734op/s; -1216176.124op/s] or [-6.850%; -6.747%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

  • 🟩 execution_time [-7.059µs; -7.014µs] or [-13.501%; -13.415%]
  • 🟩 throughput [+2963829.509op/s; +2985115.816op/s] or [+15.496%; +15.608%]

scenario:datadog_sample_span/multiple_rules_last_match/wall_time

  • 🟥 execution_time [+13.809ns; +13.973ns] or [+6.965%; +7.048%]

scenario:redis/obfuscate_redis_string

  • 🟥 execution_time [+3.428µs; +3.951µs] or [+10.349%; +11.927%]

scenario:tags/replace_trace_tags

  • 🟥 execution_time [+432.013ns; +441.672ns] or [+18.264%; +18.672%]

scenario:trace_buffer/4_senders/no_delay

  • 🟥 execution_time [+189.372µs; +218.113µs] or [+8.304%; +9.564%]
  • 🟥 throughput [-140724.974op/s; -121518.716op/s] or [-8.902%; -7.687%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

@Aaalibaba42 Aaalibaba42 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I reopened a few things you seem to have closed eagerly without saying why nor fixing the code, but overall it looks good enough after those are either fixed or justified

@anais-raison
anais-raison requested a review from a team as a code owner July 15, 2026 12:49
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot merged commit 407f8f2 into main Jul 15, 2026
112 checks passed
@gh-worker-dd-mergequeue-cf854d
gh-worker-dd-mergequeue-cf854d Bot deleted the anais/encoder-v1-to-v04-and-refacto-2 branch July 15, 2026 14:28
gh-worker-dd-mergequeue-cf854d Bot pushed a commit that referenced this pull request Jul 17, 2026
# What does this PR do?

Adds a V1 msgpack decoder in `libdd-trace-utils` and wires the V1 variant through the trace pipeline so any V1 payload can be decoded, inspected, and re-encoded.

# Motivation

[APMSP-2813](https://datadoghq.atlassian.net/browse/APMSP-2813) : Prerequisite for the sidecar V1-native path. Splitting out the `libdd-trace-utils` / `libdd-data-pipeline` plumbing so it can land before the sidecar wiring.

# Additional Notes

- Mirrors the existing v04 decoder structure.
- `trace_serializer.rs` now dispatches on `(TraceChunks, OutputFormat)`; the existing v0.4 → V1 cross-encode path is preserved.
- `trace_utils::collect_trace_chunks` renamed to `convert_trace_chunks_v04_to_v05`.

[APMSP-2813]: https://datadoghq.atlassian.net/browse/APMSP-2813?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

⚠️ You can focus on those folders/files only as I merged the others from the PR #2145 to get all the refactors: 
- libdd-data-pipeline/src/trace_exporter/trace_serializer.rs
- libdd-trace-utils/src/msgpack_decoder/
- libdd-trace-utils/src/span/mod.rs
- libdd-trace-utils/src/span/vec_map.rs
- libdd-trace-utils/src/trace_utils.rs
- libdd-trace-utils/src/tracer_payload.rs
- libdd-trace-utils/tests/snapshots/compare_v1_full_payload_snapshot_test.json
- libdd-trace-utils/tests/test_send_data.rs

Co-authored-by: anais.raison <anais.raison@datadoghq.com>
hoolioh added a commit that referenced this pull request Aug 7, 2026
…er-flare (#2332)

# Release proposal for libdd-ffe, libdd-http-client, libdd-tracer-flare
and their dependencies

This PR contains version bumps based on public API changes and commits
since last release.

## libdd-capabilities
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-v3.0.0`

### Commits

- fix(telemetry)!: stop sending Connection: close to the Agent (#2286)
- feat(capabilities)!: Add streaming to http capabilities (#2251)
- feat: added file capability [APMSP-3780] (#2240)
- feat: added environment capability [APMSP-3780] (#2239)

## libdd-common
**Next version:** `5.1.1`
**Semver bump:** `patch`
**Tag:** `libdd-common-v5.1.1`

### Commits

- feat(telemetry)!: Add Installation signature and AppProduct changes
payloads (#2213)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- test: stabilize flaky tests (#2256)
- fix(sidecar): don't double-encode file:// telemetry endpoints (#2230)
- fix: last new clippy lint (#2221)

## libdd-tinybytes
**Next version:** `1.1.2`
**Semver bump:** `patch`
**Tag:** `libdd-tinybytes-v1.1.2`

### Commits

- chore: moving to workspace-level dependencies, phase 2 (#2270)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)

## libdd-trace-protobuf
**Next version:** `4.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-trace-protobuf-v4.0.1`

### Commits

- 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)
- feat(stats)!: implement additional metric tags in libdd-trace-stats
(#2170)

## libdd-capabilities-impl
**Next version:** `4.0.0`
**Semver bump:** `major`
**Tag:** `libdd-capabilities-impl-v4.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^2.1.0 → ^3.0.0

### Commits

- feat(telemetry)!: Add Installation signature and AppProduct changes
payloads (#2213)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- fix(telemetry)!: stop sending Connection: close to the Agent (#2286)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- feat(capabilities)!: Add streaming to http capabilities (#2251)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- feat: added file capability [APMSP-3780] (#2240)
- feat(telemetry)!: make telemetry worker wasm-compatible for the
TraceExporter (#2172)
- feat: added environment capability [APMSP-3780] (#2239)

## libdd-http-client
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-http-client-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


## libdd-trace-normalization
**Next version:** `3.0.1`
**Semver bump:** `patch`
**Tag:** `libdd-trace-normalization-v3.0.1`

### Commits

- refactor: migrate to workspace dependencies, phase 4 (#2296)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)

## libdd-remote-config
**Next version:** `3.0.0`
**Semver bump:** `major`
**Tag:** `libdd-remote-config-v3.0.0`

### Commits

- refactor(rc)!: make conversion from RemoteConfigProduct back and forth
generally available (#2325)
- fix(wasm)!: finish the WASM port of remote-config (#2315)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- feat(rc): Handle expired config status (#2274)
- feat(remote-config)!: add AsmRawResponseBody capability (#2278)
- chore: moving to workspace-level dependencies, phase 2 (#2270)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- fix(rc): Make Target fields available again after eaf5ad0 (#2232)
- fix: new clippy lints (#2219)

## libdd-trace-utils
**Next version:** `10.0.0`
**Semver bump:** `major`
**Tag:** `libdd-trace-utils-v10.0.0`

### ⚠️ major bump forced due to:

- `libdd-capabilities`: ^2.1.0 → ^3.0.0

### Commits

- refactor(rc)!: make conversion from RemoteConfigProduct back and forth
generally available (#2325)
- fix(libdd-trace-utils): apply SpanLink flags masking when v0.5 json
encoding (#2314)
- refactor: migrate to workspace dependencies, phase 4 (#2296)
- feat(data-pipeline)!: add compression option for agentless export
(#2205)
- refactor: migrate to workspace dependencies, phase 3 (#2283)
- refactor(trace-utils)!: split generic TracerHeaderTags (#2279)
- chore(lint): update nightly (#2281)
- chore: moving to workspace-level dependencies, phase 2 (#2270)
- fix(remote-config)!: Expose HttpClientCapability in remote config
(#2252)
- refactor: consolidate core dependencies at workspace level (phase 1)
(#2253)
- feat(stats)!: implement additional metric tags in libdd-trace-stats
(#2170)
- 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)

## libdd-ffe
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-ffe-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


## libdd-tracer-flare
**Next version:** `1.0.0`
**Semver bump:** `major`
**Tag:** `libdd-tracer-flare-v1.0.0`

**Warning:** this is an initial release. Please verify that the version
and commits included are correct.


[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ
[APMSP-3780]:
https://datadoghq.atlassian.net/browse/APMSP-3780?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>
hoolioh added a commit that referenced this pull request Aug 18, 2026
)

# 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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants