perf(trace-exporter): forward encoded v0.4 payloads by BridgeAR · Pull Request #2362 · DataDog/libdatadog

BridgeAR · 2026-08-17T21:49:12Z

Already-finalized v0.4 payloads currently pay for a full decode and serialization before agent transport. This forwards them unchanged when no configured consumer needs span objects.

Stats, trace filters, alternate formats, log output, agentless export, and OTLP keep the decoded path.

Already-finalized v0.4 payloads otherwise pay for a full decode and serialization before agent transport. Forward them unchanged when no configured consumer needs span objects, and keep the decoded path for stats, filters, alternate formats, log output, agentless, and OTLP.

github-actions · 2026-08-17T21:51:10Z

📚 Documentation Check Results

⚠️ 3141 documentation warning(s) found

📦 `libdd-data-pipeline` - 1282 warning(s)

📦 `libdd-trace-normalization` - 244 warning(s)

📦 `libdd-trace-obfuscation` - 851 warning(s)

📦 `libdd-trace-utils` - 764 warning(s)

Updated: 2026-08-18 10:27:38 UTC | Commit: 79b8c50 | missing-docs job results

github-actions · 2026-08-17T21:52:31Z

🔒 Cargo Deny Results

⚠️ 12 issue(s) found, showing only errors (advisories, bans, sources)

📦 `libdd-data-pipeline` - 4 error(s)

Show output

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:77:1
   │
77 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── libdd-common v5.2.0
                     │   ├── libdd-capabilities-impl v4.0.0
                     │   │   ├── libdd-data-pipeline v7.0.0
                     │   │   ├── libdd-shared-runtime v2.0.0
                     │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   ├── libdd-dogstatsd-client v4.0.0
                     │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   │   └── libdd-trace-stats v6.0.0
                     │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   ├── libdd-telemetry v6.0.0
                     │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   │   │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   │   │   └── libdd-trace-stats v6.0.0 (*)
                     │   │   ├── (dev) libdd-telemetry v6.0.0 (*)
                     │   │   ├── libdd-trace-stats v6.0.0 (*)
                     │   │   └── libdd-trace-utils v10.1.0
                     │   │       ├── libdd-data-pipeline v7.0.0 (*)
                     │   │       ├── libdd-trace-obfuscation v5.0.0
                     │   │       │   └── libdd-trace-stats v6.0.0 (*)
                     │   │       ├── libdd-trace-stats v6.0.0 (*)
                     │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   ├── libdd-dogstatsd-client v4.0.0 (*)
                     │   ├── libdd-shared-runtime v2.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   ├── libdd-trace-obfuscation v5.0.0 (*)
                     │   ├── libdd-trace-stats v6.0.0 (*)
                     │   └── libdd-trace-utils v10.1.0 (*)
                     ├── (dev) libdd-data-pipeline v7.0.0 (*)
                     ├── (dev) libdd-ddsketch v1.1.0
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   ├── libdd-telemetry v6.0.0 (*)
                     │   └── libdd-trace-stats v6.0.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.1
                     │   ├── libdd-data-pipeline v7.0.0 (*)
                     │   └── libdd-trace-utils v10.1.0 (*)
                     ├── (dev) libdd-trace-obfuscation v5.0.0 (*)
                     ├── (dev) libdd-trace-stats v6.0.0 (*)
                     └── (dev) libdd-trace-utils v10.1.0 (*)

error[vulnerability]: h2 unbounded empty DATA frames
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:117:1
    │
117 │ h2 0.4.6 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0258
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0258
    ├ The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit.
      If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
      
      Low severity.
      
      Patched in v0.4.16.
    ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-q83h-524g-xf6h
    ├ Solution: Upgrade to >=0.4.16 (try `cargo update -p h2`)
    ├ h2 v0.4.6
      └── hyper v1.6.0
          ├── httpmock v0.8.0-alpha.1
          │   ├── (dev) libdd-data-pipeline v7.0.0
          │   ├── (dev) libdd-telemetry v6.0.0
          │   │   ├── libdd-data-pipeline v7.0.0 (*)
          │   │   └── libdd-trace-stats v6.0.0
          │   │       └── libdd-data-pipeline v7.0.0 (*)
          │   ├── (dev) libdd-trace-stats v6.0.0 (*)
          │   └── libdd-trace-utils v10.1.0
          │       ├── libdd-data-pipeline v7.0.0 (*)
          │       ├── libdd-trace-obfuscation v5.0.0
          │       │   └── libdd-trace-stats v6.0.0 (*)
          │       ├── libdd-trace-stats v6.0.0 (*)
          │       └── (dev) libdd-trace-utils v10.1.0 (*)
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v5.2.0
          │       ├── libdd-capabilities-impl v4.0.0
          │       │   ├── libdd-data-pipeline v7.0.0 (*)
          │       │   ├── libdd-shared-runtime v2.0.0
          │       │   │   ├── libdd-data-pipeline v7.0.0 (*)
          │       │   │   ├── libdd-dogstatsd-client v4.0.0
          │       │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
          │       │   │   │   └── libdd-trace-stats v6.0.0 (*)
          │       │   │   ├── libdd-telemetry v6.0.0 (*)
          │       │   │   └── libdd-trace-stats v6.0.0 (*)
          │       │   ├── (dev) libdd-telemetry v6.0.0 (*)
          │       │   ├── libdd-trace-stats v6.0.0 (*)
          │       │   └── libdd-trace-utils v10.1.0 (*)
          │       ├── libdd-data-pipeline v7.0.0 (*)
          │       ├── libdd-dogstatsd-client v4.0.0 (*)
          │       ├── libdd-shared-runtime v2.0.0 (*)
          │       ├── libdd-telemetry v6.0.0 (*)
          │       ├── libdd-trace-obfuscation v5.0.0 (*)
          │       ├── libdd-trace-stats v6.0.0 (*)
          │       └── libdd-trace-utils v10.1.0 (*)
          ├── hyper-util v0.1.17
          │   ├── httpmock v0.8.0-alpha.1 (*)
          │   ├── hyper-rustls v0.27.7 (*)
          │   └── libdd-common v5.2.0 (*)
          ├── libdd-common v5.2.0 (*)
          └── libdd-trace-utils v10.1.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:223:1
    │
223 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── libdd-common v5.2.0
      │   ├── libdd-capabilities-impl v4.0.0
      │   │   ├── libdd-data-pipeline v7.0.0
      │   │   ├── libdd-shared-runtime v2.0.0
      │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   ├── libdd-dogstatsd-client v4.0.0
      │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v6.0.0
      │   │   │   │       └── libdd-data-pipeline v7.0.0 (*)
      │   │   │   ├── libdd-telemetry v6.0.0
      │   │   │   │   ├── libdd-data-pipeline v7.0.0 (*)
      │   │   │   │   └── libdd-trace-stats v6.0.0 (*)
      │   │   │   └── libdd-trace-stats v6.0.0 (*)
      │   │   ├── (dev) libdd-telemetry v6.0.0 (*)
      │   │   ├── libdd-trace-stats v6.0.0 (*)
      │   │   └── libdd-trace-utils v10.1.0
      │   │       ├── libdd-data-pipeline v7.0.0 (*)
      │   │       ├── libdd-trace-obfuscation v5.0.0
      │   │       │   └── libdd-trace-stats v6.0.0 (*)
      │   │       ├── libdd-trace-stats v6.0.0 (*)
      │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   ├── libdd-dogstatsd-client v4.0.0 (*)
      │   ├── libdd-shared-runtime v2.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   ├── libdd-trace-obfuscation v5.0.0 (*)
      │   ├── libdd-trace-stats v6.0.0 (*)
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── (dev) libdd-data-pipeline v7.0.0 (*)
      ├── (dev) libdd-ddsketch v1.1.0
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   ├── libdd-telemetry v6.0.0 (*)
      │   └── libdd-trace-stats v6.0.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.1
      │   ├── libdd-data-pipeline v7.0.0 (*)
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── (dev) libdd-trace-stats v6.0.0 (*)
      ├── libdd-trace-utils v10.1.0 (*)
      └── proptest v1.5.0
          ├── (dev) libdd-common v5.2.0 (*)
          └── (dev) libdd-tinybytes v1.1.2
              ├── libdd-data-pipeline v7.0.0 (*)
              ├── (dev) libdd-tinybytes v1.1.2 (*)
              └── libdd-trace-utils v10.1.0 (*)

error[vulnerability]: Denial of Service via Stack Exhaustion
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:295:1
    │
295 │ time 0.3.41 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0009
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0009
    ├ ## Impact
      
      When user-provided input is provided to any type that parses with the RFC 2822 format, a denial of
      service attack via stack exhaustion is possible. The attack relies on formally deprecated and
      rarely-used features that are part of the RFC 2822 format used in a malicious manner. Ordinary,
      non-malicious input will never encounter this scenario.
      
      ## Patches
      
      A limit to the depth of recursion was added in v0.3.47. From this version, an error will be returned
      rather than exhausting the stack.
      
      ## Workarounds
      
      Limiting the length of user input is the simplest way to avoid stack exhaustion, as the amount of
      the stack consumed would be at most a factor of the length of the input.
    ├ Announcement: https://github.com/time-rs/time/blob/main/CHANGELOG.md#0347-2026-02-05
    ├ Solution: Upgrade to >=0.3.47 (try `cargo update -p time`)
    ├ time v0.3.41
      └── tracing-appender v0.2.3
          └── libdd-log v1.0.0
              └── (dev) libdd-data-pipeline v7.0.0

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-normalization` - 2 error(s)

Show output

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:19:1
   │
19 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     └── (dev) libdd-trace-normalization v3.0.1

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:51:1
   │
51 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
   │
   ├ ID: RUSTSEC-2026-0097
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
   ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
     
     - The `log` and `thread_rng` features are enabled
     - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
     - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
     - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
     - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
     
     `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
   ├ Announcement: https://github.com/rust-random/rand/pull/1763
   ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
   ├ rand v0.8.5
     └── (dev) libdd-trace-normalization v3.0.1

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-obfuscation` - 3 error(s)

Show output

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:64:1
   │
64 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── libdd-common v5.2.0
                     │   ├── libdd-capabilities-impl v4.0.0
                     │   │   └── libdd-trace-utils v10.1.0
                     │   │       ├── libdd-trace-obfuscation v5.0.0
                     │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
                     │   ├── libdd-trace-obfuscation v5.0.0 (*)
                     │   └── libdd-trace-utils v10.1.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.1
                     │   └── libdd-trace-utils v10.1.0 (*)
                     ├── (dev) libdd-trace-obfuscation v5.0.0 (*)
                     └── (dev) libdd-trace-utils v10.1.0 (*)

error[vulnerability]: h2 unbounded empty DATA frames
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:101:1
    │
101 │ h2 0.4.6 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
    │
    ├ ID: RUSTSEC-2026-0258
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0258
    ├ The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit.
      If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
      
      Low severity.
      
      Patched in v0.4.16.
    ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-q83h-524g-xf6h
    ├ Solution: Upgrade to >=0.4.16 (try `cargo update -p h2`)
    ├ h2 v0.4.6
      └── hyper v1.6.0
          ├── httpmock v0.8.0-alpha.1
          │   └── libdd-trace-utils v10.1.0
          │       ├── libdd-trace-obfuscation v5.0.0
          │       └── (dev) libdd-trace-utils v10.1.0 (*)
          ├── hyper-rustls v0.27.7
          │   └── libdd-common v5.2.0
          │       ├── libdd-capabilities-impl v4.0.0
          │       │   └── libdd-trace-utils v10.1.0 (*)
          │       ├── libdd-trace-obfuscation v5.0.0 (*)
          │       └── libdd-trace-utils v10.1.0 (*)
          ├── hyper-util v0.1.17
          │   ├── httpmock v0.8.0-alpha.1 (*)
          │   ├── hyper-rustls v0.27.7 (*)
          │   └── libdd-common v5.2.0 (*)
          ├── libdd-common v5.2.0 (*)
          └── libdd-trace-utils v10.1.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:189:1
    │
189 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v5.2.0
      │   ├── libdd-capabilities-impl v4.0.0
      │   │   └── libdd-trace-utils v10.1.0
      │   │       ├── libdd-trace-obfuscation v5.0.0
      │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
      │   ├── libdd-trace-obfuscation v5.0.0 (*)
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.1
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── libdd-trace-utils v10.1.0 (*)
      └── proptest v1.5.0
          ├── (dev) libdd-common v5.2.0 (*)
          └── (dev) libdd-tinybytes v1.1.2
              ├── (dev) libdd-tinybytes v1.1.2 (*)
              └── libdd-trace-utils v10.1.0 (*)

advisories FAILED, bans ok, sources ok

📦 `libdd-trace-utils` - 3 error(s)

Show output

error[vulnerability]: Invalid pointer dereference in `fmt::Pointer` impl for `Atomic` and `Shared` when the underlying pointer is invalid
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:63:1
   │
63 │ crossbeam-epoch 0.9.18 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0204
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0204
   ├ Affected versions of `fmt::Display` dereference the underlying pointer. This causes a invalid pointer dereference e.g., when a pointer created with `Atomic::null` or `Shared::null`. `fmt::Debug` impls and pre-0.9 `fmt::Display` impls, which do not dereference pointers, are not affected by this issue.
   ├ Announcement: https://github.com/crossbeam-rs/crossbeam/pull/1276
   ├ Solution: Upgrade to >=0.9.20 (try `cargo update -p crossbeam-epoch`)
   ├ crossbeam-epoch v0.9.18
     └── crossbeam-deque v0.8.5
         └── rayon-core v1.12.1
             └── rayon v1.10.0
                 └── criterion v0.5.1
                     ├── libdd-common v5.2.0
                     │   ├── libdd-capabilities-impl v4.0.0
                     │   │   └── libdd-trace-utils v10.1.0
                     │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
                     │   └── libdd-trace-utils v10.1.0 (*)
                     ├── (dev) libdd-trace-normalization v3.0.1
                     │   └── libdd-trace-utils v10.1.0 (*)
                     └── (dev) libdd-trace-utils v10.1.0 (*)

error[vulnerability]: h2 unbounded empty DATA frames
   ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:97:1
   │
97 │ h2 0.4.6 registry+https://github.com/rust-lang/crates.io-index
   │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ security vulnerability detected
   │
   ├ ID: RUSTSEC-2026-0258
   ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0258
   ├ The h2 crate, used internally by hyper, had a flaw that would accept and queue empty DATA frames without limit.
     If streams were not actively drained, this could lead to unbounded memory usage, or a panic if the length overflows.
     
     Low severity.
     
     Patched in v0.4.16.
   ├ Announcement: https://github.com/hyperium/hyper/security/advisories/GHSA-q83h-524g-xf6h
   ├ Solution: Upgrade to >=0.4.16 (try `cargo update -p h2`)
   ├ h2 v0.4.6
     └── hyper v1.6.0
         ├── httpmock v0.8.0-alpha.1
         │   └── libdd-trace-utils v10.1.0
         │       └── (dev) libdd-trace-utils v10.1.0 (*)
         ├── hyper-rustls v0.27.7
         │   └── libdd-common v5.2.0
         │       ├── libdd-capabilities-impl v4.0.0
         │       │   └── libdd-trace-utils v10.1.0 (*)
         │       └── libdd-trace-utils v10.1.0 (*)
         ├── hyper-util v0.1.17
         │   ├── httpmock v0.8.0-alpha.1 (*)
         │   ├── hyper-rustls v0.27.7 (*)
         │   └── libdd-common v5.2.0 (*)
         ├── libdd-common v5.2.0 (*)
         └── libdd-trace-utils v10.1.0 (*)

error[unsound]: Rand is unsound with a custom logger using `rand::rng()`
    ┌─ /home/runner/work/libdatadog/libdatadog/Cargo.lock:184:1
    │
184 │ rand 0.8.5 registry+https://github.com/rust-lang/crates.io-index
    │ ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ unsound advisory detected
    │
    ├ ID: RUSTSEC-2026-0097
    ├ Advisory: https://rustsec.org/advisories/RUSTSEC-2026-0097
    ├ It has been reported (by [@lopopolo](https://github.com/lopopolo)) that the `rand` library is [unsound](https://rust-lang.github.io/unsafe-code-guidelines/glossary.html#soundness-of-code--of-a-library) (i.e. that safe code using the public API can cause Undefined Behaviour) when all the following conditions are met:
      
      - The `log` and `thread_rng` features are enabled
      - A [custom logger](https://docs.rs/log/latest/log/#implementing-a-logger) is defined
      - The custom logger accesses `rand::rng()` (previously `rand::thread_rng()`) and calls any `TryRng` (previously `RngCore`) methods on `ThreadRng`
      - The `ThreadRng` (attempts to) reseed while called from the custom logger (this happens every 64 kB of generated data)
      - Trace-level logging is enabled or warn-level logging is enabled and the random source (the `getrandom` crate) is unable to provide a new seed
      
      `TryRng` (previously `RngCore`) methods for `ThreadRng` use `unsafe` code to cast `*mut BlockRng<ReseedingCore>` to `&mut BlockRng<ReseedingCore>`. When all the above conditions are met this results in an aliased mutable reference, violating the Stacked Borrows rules. Miri is able to detect this violation in sample code. Since construction of [aliased mutable references is Undefined Behaviour](https://doc.rust-lang.org/stable/nomicon/references.html), the behaviour of optimized builds is hard to predict.
    ├ Announcement: https://github.com/rust-random/rand/pull/1763
    ├ Solution: Upgrade to >=0.10.1 OR <0.10.0, >=0.9.3 OR <0.9.0, >=0.8.6 (try `cargo update -p rand`)
    ├ rand v0.8.5
      ├── (dev) libdd-common v5.2.0
      │   ├── libdd-capabilities-impl v4.0.0
      │   │   └── libdd-trace-utils v10.1.0
      │   │       └── (dev) libdd-trace-utils v10.1.0 (*)
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── (dev) libdd-trace-normalization v3.0.1
      │   └── libdd-trace-utils v10.1.0 (*)
      ├── libdd-trace-utils v10.1.0 (*)
      └── proptest v1.5.0
          ├── (dev) libdd-common v5.2.0 (*)
          └── (dev) libdd-tinybytes v1.1.2
              ├── (dev) libdd-tinybytes v1.1.2 (*)
              └── libdd-trace-utils v10.1.0 (*)

advisories FAILED, bans ok, sources ok

Updated: 2026-08-18 10:29:19 UTC | Commit: 79b8c50 | dependency-check job results

datadog-datadog-us1-prod · 2026-08-17T22:01:46Z

⚠️ Warnings

🚦 2 Pipeline jobs failed

semver-check | validate — 🔧 Needs a code fix, caused by this PR

View in Datadog · View in GitHub Actions

SEMVER validation failed due to breaking changes in 'libdd-data-pipeline'. Public method parameter count changed and package feature 'libdd-trace-obfuscation' was removed

Required checks pass | allchecks

View in Datadog · View in GitHub Actions

Job failed. Some checks have failed or timed out.
📋 Copy prompt for your agent
CI on my pull request is failing. Help me find and fix the root cause of each failing job below — they were flagged as caused by changes in this PR, so focus on the diff. For each job, explain the failure and propose a fix.

Branch: BridgeAR/2026-08-17-bulk-finalized-spans

semver-check | validate
Commit: 79b8c507d2c950f241fbf05ad5b5894829b6506e
Error (code / build):
SEMVER validation failed due to breaking changes in 'libdd-data-pipeline'. Public method parameter count changed and package feature 'libdd-trace-obfuscation' was removed
CI job: https://github.com/DataDog/libdatadog/actions/runs/32126681645/job/95681405104

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 93.88%
• Overall Coverage: 76.81% (+0.34%)

Useful? React with 👍 / 👎

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

🔗 Commit SHA: 4e4cf37 | Docs | View more details | Give us feedback!}

Direct intake bypasses the Agent normalization and obfuscation, which can send malformed or sensitive span data unchanged. Agentless setup now requires an explicit obfuscation configuration and rejects invalid replacement rules before export.

Embedded runtimes cannot expose host environment variables through std::env, so obfuscation defaults and replacement rules would be absent. The platform-capability constructor uses the native parser and propagates provider or rule errors before export.

dd-octo-sts · 2026-08-18T01:01:33Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.20 MB	8.20 MB	-0% (-144 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.46 MB	89.04 MB	--.47% (-431.70 KB) 💪

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.06 MB	11.05 MB	--.11% (-12.49 KB) 💪
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.63 MB	100.21 MB	--.42% (-438.25 KB) 💪

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.62 MB	26.43 MB	--.69% (-189.00 KB) 💪
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	180.67 MB	180.13 MB	--.29% (-552.00 KB) 💪
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	772.95 MB	771.93 MB	--.13% (-1.02 MB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.72 MB	8.67 MB	--.63% (-56.50 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.56 KB	94.56 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.64 MB	25.48 MB	--.60% (-160.00 KB) 💪
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.05 MB	50.78 MB	--.53% (-277.71 KB) 💪

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.20 MB	23.01 MB	--.79% (-189.00 KB) 💪
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	185.55 MB	184.98 MB	--.31% (-592.00 KB) 💪
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	759.55 MB	759.31 MB	--.03% (-250.09 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.74 MB	6.69 MB	--.73% (-50.50 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.04 KB	96.04 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.58 MB	27.40 MB	--.65% (-184.00 KB) 💪
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.60 MB	48.33 MB	--.54% (-269.14 KB) 💪

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.72 MB	79.30 MB	--.53% (-436.54 KB) 💪
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.15 MB	9.11 MB	--.47% (-44.15 KB) 💪

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.39 MB	94.95 MB	--.46% (-454.18 KB) 💪
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.16 MB	11.11 MB	--.50% (-57.32 KB) 💪

pr-commenter · 2026-08-18T01:11:21Z

Benchmarks

Comparison

Benchmark execution time: 2026-08-18 11:00:11

Comparing candidate commit 4e4cf37 in PR branch BridgeAR/2026-08-17-bulk-finalized-spans with baseline commit 899d0fb in branch main.

Found 13 performance improvements and 19 performance regressions! Performance is the same for 108 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/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...

🟩 execution_time [-20.061µs; -19.903µs] or [-9.752%; -9.675%]
🟩 throughput [+520972.372op/s; +524945.646op/s] or [+10.717%; +10.799%]

scenario:normalization/normalize_name/normalize_name/bad-name

🟩 execution_time [-1.517µs; -1.459µs] or [-7.993%; -7.683%]
🟩 throughput [+4392585.696op/s; +4557490.432op/s] or [+8.338%; +8.651%]

scenario:normalization/normalize_name/normalize_name/good

🟩 execution_time [-1.140µs; -1.088µs] or [-10.216%; -9.750%]
🟩 throughput [+9709313.673op/s; +10151554.378op/s] or [+10.832%; +11.325%]

scenario:normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...

🟩 execution_time [-38.748µs; -38.470µs] or [-7.221%; -7.169%]
🟩 throughput [+143979.892op/s; +145002.398op/s] or [+7.726%; +7.781%]

scenario:normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters

🟩 execution_time [-27.128µs; -27.013µs] or [-13.833%; -13.774%]
🟩 throughput [+814933.188op/s; +818256.129op/s] or [+15.981%; +16.047%]

scenario:normalization/normalize_service/normalize_service/[empty string]

🟥 execution_time [+3.229µs; +3.256µs] or [+9.020%; +9.097%]
🟥 throughput [-2330568.094op/s; -2310349.344op/s] or [-8.342%; -8.270%]

scenario:otlp/encode_json/1x1000

🟩 execution_time [-132.996µs; -131.875µs] or [-6.613%; -6.558%]

scenario:vec_map/as_deduped_map/already_deduped/16

🟥 execution_time [+5.611ns; +5.631ns] or [+22.143%; +22.222%]

scenario:vec_map/as_deduped_map/already_deduped/8

🟩 execution_time [-1.811ns; -1.797ns] or [-11.545%; -11.458%]

scenario:vec_map/contains_key/8

🟥 execution_time [+4.154ns; +4.327ns] or [+5.725%; +5.964%]
🟥 throughput [-6207604.541op/s; -5967086.729op/s] or [-5.630%; -5.411%]

scenario:vec_map/get_hit/128

🟥 execution_time [+4.301µs; +4.310µs] or [+34.829%; +34.897%]
🟥 throughput [-2682029.487op/s; -2676687.419op/s] or [-25.876%; -25.825%]

scenario:vec_map/get_hit/16

🟥 execution_time [+36.960ns; +37.142ns] or [+17.385%; +17.470%]
🟥 throughput [-11198203.003op/s; -11140508.810op/s] or [-14.880%; -14.803%]

scenario:vec_map/get_hit/64

🟥 execution_time [+980.021ns; +982.194ns] or [+28.764%; +28.828%]
🟥 throughput [-4204089.049op/s; -4195604.052op/s] or [-22.381%; -22.335%]

scenario:vec_map/get_hit/8

🟥 execution_time [+5.244ns; +5.341ns] or [+8.584%; +8.744%]
🟥 throughput [-10547802.879op/s; -10344371.197op/s] or [-8.053%; -7.898%]

scenario:vec_map/get_miss/8

🟩 execution_time [-1.832ns; -1.809ns] or [-24.401%; -24.090%]

scenario:vec_map/iter/128

🟥 execution_time [+7.164ns; +7.231ns] or [+6.894%; +6.958%]
🟥 throughput [-80137970.762op/s; -79423791.417op/s] or [-6.506%; -6.448%]

scenario:vec_map/iter/16

🟥 execution_time [+0.597ns; +0.604ns] or [+4.568%; +4.624%]
🟥 throughput [-54133127.499op/s; -53462355.668op/s] or [-4.422%; -4.367%]

scenario:vec_map/iter/8

🟥 execution_time [+0.550ns; +0.556ns] or [+8.223%; +8.318%]
🟥 throughput [-92012223.532op/s; -90885976.278op/s] or [-7.687%; -7.593%]

Benchmark execution time: 2026-08-18 11:09:34

Comparing candidate commit 4e4cf37 in PR branch BridgeAR/2026-08-17-bulk-finalized-spans with baseline commit 899d0fb in branch main.

Found 9 performance improvements and 15 performance regressions! Performance is the same for 156 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/system/4096

🟩 execution_time [-8.933ns; -8.743ns] or [-9.577%; -9.374%]

scenario:credit_card/is_card_number/ 378282246310005

🟥 execution_time [+5.490µs; +5.571µs] or [+8.059%; +8.177%]
🟥 throughput [-1109757.123op/s; -1094416.296op/s] or [-7.560%; -7.455%]

scenario:credit_card/is_card_number/378282246310005

🟥 execution_time [+4.987µs; +5.062µs] or [+7.667%; +7.783%]
🟥 throughput [-1110134.312op/s; -1094521.683op/s] or [-7.221%; -7.119%]

scenario:credit_card/is_card_number/37828224631000521389798

🟥 execution_time [+6.665µs; +6.691µs] or [+14.577%; +14.634%]
🟥 throughput [-2793106.163op/s; -2781321.848op/s] or [-12.771%; -12.717%]

scenario:credit_card/is_card_number/x371413321323331

🟩 execution_time [-976.712ns; -962.125ns] or [-14.268%; -14.055%]
🟩 throughput [+23903141.044op/s; +24324591.552op/s] or [+16.363%; +16.651%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

🟥 execution_time [+4.081µs; +4.115µs] or [+7.628%; +7.693%]
🟥 throughput [-1335403.301op/s; -1324824.153op/s] or [-7.143%; -7.087%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

🟥 execution_time [+4.636µs; +4.700µs] or [+9.220%; +9.349%]
🟥 throughput [-1700087.965op/s; -1678645.458op/s] or [-8.548%; -8.440%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

🟥 execution_time [+6.665µs; +6.691µs] or [+14.579%; +14.636%]
🟥 throughput [-2793664.243op/s; -2782042.081op/s] or [-12.772%; -12.719%]

scenario:credit_card/is_card_number_no_luhn/x371413321323331

🟩 execution_time [-970.625ns; -954.795ns] or [-14.179%; -13.948%]
🟩 throughput [+23693097.052op/s; +24149537.396op/s] or [+16.219%; +16.532%]

scenario:datadog_sample_span/multiple_rules_last_match/wall_time

🟥 execution_time [+17.131ns; +17.219ns] or [+8.717%; +8.762%]

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

🟩 execution_time [-2.564ns; -2.472ns] or [-8.753%; -8.437%]

scenario:glob_matcher/ascii_exact_match/wall_time

🟩 execution_time [-2.538ns; -2.484ns] or [-8.673%; -8.490%]

scenario:glob_matcher/ascii_exact_miss/wall_time

🟩 execution_time [-2.986ns; -2.907ns] or [-20.969%; -20.412%]

scenario:glob_matcher/ascii_pattern_unicode_subject/wall_time

🟥 execution_time [+6.295ns; +6.361ns] or [+4.615%; +4.664%]

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

🟥 execution_time [+5.365ns; +5.606ns] or [+4.359%; +4.555%]

scenario:profiler_attached/fast_path_system/4096

🟩 execution_time [-5.690ns; -5.459ns] or [-5.437%; -5.216%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

…ulk-finalized-spans

The agentless path rebuilt v0.4 spans after normalization and obfuscation only to serialize them as JSON, allocating a second set of map containers. A 5,000-span Express-shaped batch dropped from 7.05 ms to 5.59 ms (-20.7%) in the middle-five mean of seven release-mode trials. A fresh process reproduced 7.09 ms to 5.56 ms (-21.7%).

Top-level detection cloned every service string and allocated a map even for a single-span trace. On Rust 1.97.1, 200k spans across seven trials (drop best and worst) fell from 30.25 ms to 15.98 ms for one-span traces and 16.87 ms to 10.25 ms for four-span traces; a fresh process reproduced 29.92 to 15.81 ms and 16.90 to 10.18 ms.

The agentless intake contract uses whole Unix seconds, but the native encoder forwarded trace nanoseconds unchanged. This restores wire parity with dd-trace-js while keeping durations in nanoseconds.

Starts before 2000 enter the correction branch. std::time::SystemTime traps on wasm32-unknown-unknown, so agentless export could crash instead of normalizing the span.

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

BridgeAR added 2 commits August 18, 2026 02:18

BridgeAR added 5 commits August 18, 2026 11:27

Merge remote-tracking branch 'origin/main' into BridgeAR/2026-08-17-b…

b2d8e61

…ulk-finalized-spans

fix(agentless): encode span starts in whole seconds

0081bcb

The agentless intake contract uses whole Unix seconds, but the native encoder forwarded trace nanoseconds unchanged. This restores wire parity with dd-trace-js while keeping durations in nanoseconds.

fix(trace-normalization): use a WASM-compatible clock

4e4cf37

Starts before 2000 enter the correction branch. std::time::SystemTime traps on wasm32-unknown-unknown, so agentless export could crash instead of normalizing the span.

Navigation Menu

Uh oh!

perf(trace-exporter): forward encoded v0.4 payloads - #2362

perf(trace-exporter): forward encoded v0.4 payloads#2362
BridgeAR wants to merge 8 commits into
mainfrom
BridgeAR/2026-08-17-bulk-finalized-spans

BridgeAR commented Aug 17, 2026

Uh oh!

github-actions Bot commented Aug 17, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Aug 17, 2026 •

edited

Loading

Uh oh!

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

edited by datadog-datadog-prod-us1 Bot

Loading

Uh oh!

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

edited

Loading

Uh oh!

pr-commenter Bot commented Aug 18, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Explanation

More details about the CI and significant changes

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Uh oh!

Conversation

BridgeAR commented Aug 17, 2026

Uh oh!

github-actions Bot commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

📚 Documentation Check Results

📦 libdd-data-pipeline - 1282 warning(s)

📦 libdd-trace-normalization - 244 warning(s)

📦 libdd-trace-obfuscation - 851 warning(s)

📦 libdd-trace-utils - 764 warning(s)

Uh oh!

github-actions Bot commented Aug 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🔒 Cargo Deny Results

📦 libdd-data-pipeline - 4 error(s)

📦 libdd-trace-normalization - 2 error(s)

📦 libdd-trace-obfuscation - 3 error(s)

📦 libdd-trace-utils - 3 error(s)

Uh oh!

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

Uh oh!

⚠️ Warnings

ℹ️ Info

Uh oh!

dd-octo-sts Bot commented Aug 18, 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 Aug 18, 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:normalization/normalize_name/normalize_name/Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Long-.Too-Lo...

scenario:normalization/normalize_name/normalize_name/bad-name

scenario:normalization/normalize_name/normalize_name/good

scenario:normalization/normalize_service/normalize_service/A0000000000000000000000000000000000000000000000000...

scenario:normalization/normalize_service/normalize_service/Test Conversion 0f Weird !@#$%^&**() Characters

scenario:normalization/normalize_service/normalize_service/[empty string]

scenario:otlp/encode_json/1x1000

scenario:vec_map/as_deduped_map/already_deduped/16

scenario:vec_map/as_deduped_map/already_deduped/8

scenario:vec_map/contains_key/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

scenario:vec_map/get_miss/8

scenario:vec_map/iter/128

scenario:vec_map/iter/16

scenario:vec_map/iter/8

Explanation

More details about the CI and significant changes

scenario:alloc_free/system/4096

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:datadog_sample_span/multiple_rules_last_match/wall_time

scenario:glob_matcher/ascii_case_insensitive_match/wall_time

scenario:glob_matcher/ascii_exact_match/wall_time

scenario:glob_matcher/ascii_exact_miss/wall_time

scenario:glob_matcher/ascii_pattern_unicode_subject/wall_time

scenario:glob_matcher/unicode_pattern_wildcard_match/wall_time

scenario:profiler_attached/fast_path_system/4096

Candidate

Baseline

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

github-actions Bot commented Aug 17, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 1282 warning(s)

📦 `libdd-trace-normalization` - 244 warning(s)

📦 `libdd-trace-obfuscation` - 851 warning(s)

📦 `libdd-trace-utils` - 764 warning(s)

github-actions Bot commented Aug 17, 2026 •

edited

Loading

📦 `libdd-data-pipeline` - 4 error(s)

📦 `libdd-trace-normalization` - 2 error(s)

📦 `libdd-trace-obfuscation` - 3 error(s)

📦 `libdd-trace-utils` - 3 error(s)

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

edited by datadog-datadog-prod-us1 Bot

Loading

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

edited

Loading

pr-commenter Bot commented Aug 18, 2026 •

edited

Loading