feat(common)!: add HTTPS_PROXY support for hyper_backend by bwoebi · Pull Request #2421 · DataDog/libdatadog

bwoebi · 2026-08-26T12:23:20Z

We make sure to fetch the env vars only once at init, at basically the same time than the TLS envs are read too.

This allows users to redirect requests going to the datadog backend through egress proxies, rather than having to hack around with DNS and MITM TLS certificates.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 1f0653a08a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

datadog-official · 2026-08-26T12:31:31Z

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 70.80%
• Overall Coverage: 76.67% (+0.10%)

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

🔗 Commit SHA: 156a65e | Docs | View more details | Give us feedback!}

dd-octo-sts · 2026-08-26T12:52:54Z

Artifact Size Benchmark Report

aarch64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.so	8.26 MB	8.26 MB	0% (0 B) 👌
/aarch64-alpine-linux-musl/lib/libdatadog_profiling.a	89.74 MB	89.73 MB	-0% (-6.67 KB) 👌

aarch64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.a	100.95 MB	100.95 MB	-0% (-6.07 KB) 👌
/aarch64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.13 MB	11.13 MB	+0% (+200 B) 👌

libdatadog-x64-windows

Artifact	Baseline	Commit	Change
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.dll	26.67 MB	26.67 MB	+0% (+512 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/debug/dynamic/datadog_profiling_ffi.pdb	181.05 MB	181.03 MB	--.01% (-24.00 KB) 💪
/libdatadog-x64-windows/debug/static/datadog_profiling_ffi.lib	774.03 MB	768.50 MB	--.71% (-5.52 MB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.dll	8.75 MB	8.75 MB	--.01% (-1.50 KB) 💪
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.lib	94.96 KB	94.96 KB	0% (0 B) 👌
/libdatadog-x64-windows/release/dynamic/datadog_profiling_ffi.pdb	25.69 MB	25.69 MB	0% (0 B) 👌
/libdatadog-x64-windows/release/static/datadog_profiling_ffi.lib	51.17 MB	51.16 MB	--.01% (-7.65 KB) 💪

libdatadog-x86-windows

Artifact	Baseline	Commit	Change
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.dll	23.25 MB	23.25 MB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/debug/dynamic/datadog_profiling_ffi.pdb	186.05 MB	186.01 MB	--.02% (-40.00 KB) 💪
/libdatadog-x86-windows/debug/static/datadog_profiling_ffi.lib	761.07 MB	755.69 MB	--.70% (-5.37 MB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.dll	6.76 MB	6.76 MB	--.02% (-2.00 KB) 💪
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.lib	96.45 KB	96.45 KB	0% (0 B) 👌
/libdatadog-x86-windows/release/dynamic/datadog_profiling_ffi.pdb	27.63 MB	27.62 MB	--.02% (-8.00 KB) 💪
/libdatadog-x86-windows/release/static/datadog_profiling_ffi.lib	48.69 MB	48.69 MB	--.01% (-6.91 KB) 💪

x86_64-alpine-linux-musl

Artifact	Baseline	Commit	Change
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.a	79.98 MB	79.98 MB	+0% (+248 B) 👌
/x86_64-alpine-linux-musl/lib/libdatadog_profiling.so	9.17 MB	9.17 MB	0% (0 B) 👌

x86_64-unknown-linux-gnu

Artifact	Baseline	Commit	Change
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.a	95.71 MB	95.71 MB	+0% (+56 B) 👌
/x86_64-unknown-linux-gnu/lib/libdatadog_profiling.so	11.19 MB	11.19 MB	+0% (+344 B) 👌

pr-commenter · 2026-08-26T12:57:44Z

Benchmarks

Comparison

Benchmark execution time: 2026-08-26 19:11:53

Comparing candidate commit 0afb70f in PR branch bob/hyper-proxy with baseline commit 64436d5 in branch main.

Found 11 performance improvements and 11 performance regressions! Performance is the same for 114 metrics, 0 unstable metrics.

Explanation

This is an A/B test comparing a candidate commit's performance against that of a baseline commit. Performance changes are noted in the tables below as:

🟩 = significantly better candidate vs. baseline
🟥 = significantly worse candidate vs. baseline

We compute a confidence interval (CI) over the relative difference of means between metrics from the candidate and baseline commits, considering the baseline as the reference.

If the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD), the change is considered significant.

Feel free to reach out to #apm-benchmarking-platform on Slack if you have any questions.

More details about the CI and significant changes

You can imagine this CI as a range of values that is likely to contain the true difference of means between the candidate and baseline commits.

CIs of the difference of means are often centered around 0%, because often changes are not that big:

---------------------------------(------|---^--------)-------------------------------->
                              -0.6%    0%  0.3%     +1.2%
                                 |          |        |
         lower bound of the CI --'          |        |
sample mean (center of the CI) -------------'        |
         upper bound of the CI ----------------------'

As described above, a change is considered significant if the CI is entirely outside the configured SIGNIFICANT_IMPACT_THRESHOLD (or the deprecated UNCONFIDENCE_THRESHOLD).

For instance, for an execution time metric, this confidence interval indicates a significantly worse performance:

----------------------------------------|---------|---(---------^---------)---------->
                                       0%        1%  1.3%      2.2%      3.1%
                                                  |   |         |         |
       significant impact threshold --------------'   |         |         |
                      lower bound of CI --------------'         |         |
       sample mean (center of the CI) --------------------------'         |
                      upper bound of CI ----------------------------------'

scenario:msgpack_encoder::v04

🟥 execution_time [+523.880µs; +552.949µs] or [+4.299%; +4.538%]

scenario:otlp/e2e_json/1x1000

🟥 execution_time [+352.227µs; +354.716µs] or [+8.440%; +8.499%]

scenario:otlp/encode_json/1x1000

🟥 execution_time [+359.383µs; +361.181µs] or [+19.635%; +19.733%]

scenario:otlp/encode_protobuf/1x1000

🟩 execution_time [-48.784µs; -48.046µs] or [-4.358%; -4.292%]

scenario:vec_map/as_deduped_map/already_deduped/16

🟥 execution_time [+5.602ns; +5.635ns] or [+22.075%; +22.208%]

scenario:vec_map/as_deduped_map/already_deduped/8

🟩 execution_time [-1.818ns; -1.805ns] or [-11.580%; -11.495%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_10/8

🟩 execution_time [-17.069ns; -16.804ns] or [-4.552%; -4.481%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_2/8

🟩 execution_time [-26.633ns; -26.382ns] or [-5.423%; -5.372%]

scenario:vec_map/as_deduped_map/needs_dedup_1_in_4/8

🟩 execution_time [-22.352ns; -21.870ns] or [-5.391%; -5.275%]

scenario:vec_map/contains_key/8

🟥 execution_time [+3.386ns; +3.535ns] or [+4.537%; +4.736%]
🟥 throughput [-4846094.937op/s; -4649440.351op/s] or [-4.521%; -4.338%]

scenario:vec_map/dedup/dup_1_in_10/8

🟥 execution_time [+17.492ns; +24.648ns] or [+4.509%; +6.354%]

scenario:vec_map/get_hit/128

🟥 execution_time [+866.078ns; +875.798ns] or [+7.056%; +7.135%]
🟥 throughput [-694544.845op/s; -687120.621op/s] or [-6.661%; -6.589%]

scenario:vec_map/get_hit/16

🟩 execution_time [-12.561ns; -12.303ns] or [-5.893%; -5.772%]
🟩 throughput [+4601314.097op/s; +4695299.922op/s] or [+6.130%; +6.255%]

scenario:vec_map/get_hit/64

🟥 execution_time [+234.774ns; +238.499ns] or [+6.899%; +7.008%]
🟥 throughput [-1232440.366op/s; -1212951.012op/s] or [-6.553%; -6.450%]

scenario:vec_map/get_hit/8

🟩 execution_time [-7.287ns; -7.136ns] or [-11.907%; -11.659%]
🟩 throughput [+17286655.873op/s; +17613290.770op/s] or [+13.224%; +13.474%]

scenario:vec_map/get_miss/16

🟩 execution_time [-0.794ns; -0.718ns] or [-7.667%; -6.930%]

scenario:vec_map/get_miss/8

🟩 execution_time [-0.322ns; -0.276ns] or [-5.402%; -4.622%]

Benchmark execution time: 2026-08-26 19:11:54

Comparing candidate commit 0afb70f in PR branch bob/hyper-proxy with baseline commit 64436d5 in branch main.

Found 24 performance improvements and 2 performance regressions! Performance is the same for 81 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 [-6.078µs; -5.991µs] or [-8.248%; -8.130%]
🟩 throughput [+1202058.043op/s; +1218372.541op/s] or [+8.858%; +8.978%]

scenario:credit_card/is_card_number/378282246310005

🟩 execution_time [-6.005µs; -5.933µs] or [-8.498%; -8.396%]
🟩 throughput [+1298182.908op/s; +1312717.481op/s] or [+9.174%; +9.276%]

scenario:credit_card/is_card_number/37828224631000521389798

🟩 execution_time [-8.049µs; -8.004µs] or [-15.176%; -15.090%]
🟩 throughput [+3352861.482op/s; +3370913.995op/s] or [+17.783%; +17.879%]

scenario:credit_card/is_card_number/x371413321323331

🟩 execution_time [-742.653ns; -740.255ns] or [-11.517%; -11.480%]
🟩 throughput [+20117879.348op/s; +20182433.506op/s] or [+12.972%; +13.014%]

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

🟩 execution_time [-4.330µs; -4.137µs] or [-6.639%; -6.344%]
🟩 throughput [+1040641.069op/s; +1092304.263op/s] or [+6.787%; +7.124%]

scenario:credit_card/is_card_number_no_luhn/ 378282246310005

🟩 execution_time [-4.675µs; -4.634µs] or [-8.002%; -7.932%]
🟩 throughput [+1475148.605op/s; +1488248.123op/s] or [+8.618%; +8.695%]

scenario:credit_card/is_card_number_no_luhn/378282246310005

🟩 execution_time [-5.181µs; -5.129µs] or [-9.333%; -9.240%]
🟩 throughput [+1835519.544op/s; +1852718.184op/s] or [+10.189%; +10.284%]

scenario:credit_card/is_card_number_no_luhn/37828224631000521389798

🟩 execution_time [-8.247µs; -8.209µs] or [-15.511%; -15.438%]
🟩 throughput [+3435331.073op/s; +3450798.748op/s] or [+18.266%; +18.348%]

scenario:credit_card/is_card_number_no_luhn/x371413321323331

🟩 execution_time [-742.440ns; -739.454ns] or [-11.513%; -11.467%]
🟩 throughput [+20090229.151op/s; +20173089.297op/s] or [+12.955%; +13.009%]

scenario:datadog_sample_span/resource_pattern_rule_matching/wall_time

🟥 execution_time [+10.609ns; +10.725ns] or [+4.122%; +4.167%]

scenario:datadog_sample_span/tag_rule_matching/wall_time

🟩 execution_time [-17.189ns; -17.044ns] or [-5.023%; -4.981%]

scenario:glob_matcher/ascii_exact_miss/wall_time

🟩 execution_time [-0.861ns; -0.835ns] or [-6.965%; -6.757%]

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

🟩 execution_time [-21.423ns; -21.399ns] or [-36.797%; -36.756%]

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

🟩 execution_time [-21.391ns; -21.369ns] or [-36.742%; -36.704%]

scenario:trace_buffer/4_senders/no_delay

🟩 execution_time [-125.871µs; -100.035µs] or [-5.209%; -4.140%]
🟩 throughput [+65413.942op/s; +82558.092op/s] or [+4.389%; +5.539%]

scenario:write only interface

🟥 execution_time [+51.957ns; +54.494ns] or [+4.779%; +5.012%]

Candidate

Omitted due to size.

Baseline

Omitted due to size.

paullegranddc · 2026-08-26T17:20:52Z

Why not hyper_http_proxy which is already used in the serverless bottlecap project if we need to support this?

https://github.com/DataDog/datadog-lambda-extension/blob/fec395f5b7546d82ebde6aa149e6362bd050829b/bottlecap/src/traces/http_client.rs#L28-L29

bwoebi · 2026-08-26T17:40:43Z

@paullegranddc hyper_http_proxy doesn't really help us get rid of of most of the plumping done to abstract the connection stream away (proxy vs non-proxy stream) as it is supposed to be an optional dependency.

It would only replace the HttpsProxyConnector impl in this PR (which is pretty straighforward I'd say?) basically - and instead be wired in there.

Everything we could get from the crate is minimal, given that it would have to be integrated into our own abstractions including the tls config builder. I don't quite see that being worth the dependency.

We make sure to fetch the env vars only once at init, at basically the same time than the TLS envs are read too. This allows users to redirect requests going to the datadog backend through egress proxies, rather than having to hack around with DNS and MITM TLS certificates.

bwoebi · 2026-08-26T20:38:42Z

/merge

gh-worker-devflow-routing-ef8351 · 2026-08-26T20:38:46Z

View all feedbacks in Devflow UI.

2026-08-26 20:38:46 UTC ℹ️ Start processing command /merge

2026-08-26 20:38:50 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 53m (p90).

2026-08-26 21:14:50 UTC ℹ️ MergeQueue: This merge request was merged

…ker, libdd-data-pipeline, li... (#2482) # Release proposal for libdd-capabilities-impl, libdd-crashtracker, libdd-data-pipeline, libdd-ddsketch, libdd-ffe, libdd-http-client, libdd-ipc, libdd-library-config, libdd-live-debugger, libdd-otel-thread-ctx, libdd-remote-config, libdd-shared-runtime, libdd-telemetry, libdd-trace-utils, libdd-tracer-flare 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-common` `5.2.0` → `6.0.0` affects: `libdd-profiling`, `libdd-sampling` - `libdd-trace-utils` `11.0.0` → `12.0.0` affects: `libdd-sampling` ## libdd-capabilities **Next version:** `3.0.1` **Semver bump:** `patch` **Tag:** `libdd-capabilities-v3.0.1` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) ## libdd-common **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-common-v6.0.0` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421) ## libdd-ipc-macros **Next version:** `1.0.1` **Semver bump:** `patch` **Tag:** `libdd-ipc-macros-v1.0.1` ### Commits - feat(sidecar)!: support appsec helper-rust integration with sidecar (#2310) ## libdd-otel-thread-ctx **Next version:** `1.1.0` **Semver bump:** `minor` **Tag:** `libdd-otel-thread-ctx-v1.1.0` ### Commits - feat(otel-thread-ctx): add update-and-attach operation (#2443) ## libdd-tinybytes **Next version:** `1.1.3` **Semver bump:** `patch` **Tag:** `libdd-tinybytes-v1.1.3` ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-capabilities-impl **Next version:** `5.0.0` **Semver bump:** `major` **Tag:** `libdd-capabilities-impl-v5.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat: do not entirely disable connection pooling for periodic connections (#2440) - feat(data-pipeline): add runtime-independent agentless sending (#2389) ## libdd-http-client **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-http-client-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(common)!: add HTTPS_PROXY support for hyper_backend (#2421) ## libdd-remote-config **Next version:** `5.0.0` **Semver bump:** `major` **Tag:** `libdd-remote-config-v5.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - fix(remote-config): refresh fetcher identity (#2469) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(remote-config): reuse injected sleep capability (#2429) ## libdd-shared-runtime **Next version:** `4.0.0` **Semver bump:** `major` **Tag:** `libdd-shared-runtime-v4.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - fix(shared-runtime): allow disabling worker fork restart (#2464) ## libdd-trace-utils **Next version:** `12.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-utils-v12.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - feat(trace-utils): add v1-native JSON log encoder brick (#2371) - feat(trace-utils): add v1-native agentless JSON encoder brick (#2370) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - feat(data-pipeline): emit native trace export telemetry (#2338) - feat(data-pipeline)!: add agentless stats export (#2309) - fix(trace-utils): use vec map dedup when serializing (#2422) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - fix(compression): align zstd behavior across targets (#2400) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-ffe **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-ffe-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.1.1 → ^6.0.0 - `libdd-remote-config`: ^3.0.0 → ^4.1.0 - `libdd-trace-protobuf`: ^4.0.1 → ^5.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(ffe): support arbitrary semver core parts (#2413) - feat(ffe)!: send the split serial id on exposure events [EX-3425] (#2402) - feat(ffe): expose observeFullEvaluationData config-level FFI getter (#2373) - fix(ffe): report rejected flags as parse errors (#2339) - test: skip/shorten slow miri jobs (#2331) ## libdd-dogstatsd-client **Next version:** `6.0.0` **Semver bump:** `major` **Tag:** `libdd-dogstatsd-client-v6.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-telemetry **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-telemetry-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - refactor(telemetry): avoid doing two separate http requests in stop telemetry (#2435) ## libdd-trace-obfuscation **Next version:** `8.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-obfuscation-v8.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - fix(trace-obfuscation): scan all span meta for credit-card obfuscation (#2472) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418) ## libdd-tracer-flare **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-tracer-flare-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) ## libdd-crashtracker **Next version:** `3.0.0` **Semver bump:** `major` **Tag:** `libdd-crashtracker-v3.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(crashtracking): filter out frames above faulting frame (#2428) - feat(sidecar)!: support appsec helper-rust integration with sidecar (#2310) - chore(crashtracking): use RAII remote ptrace API (#2416) - chore(crashtracking): bump libdd-libunwind-sys to v1.0.3 (#2414) ## libdd-data-pipeline-core **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-core-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. ## libdd-trace-stats **Next version:** `9.0.0` **Semver bump:** `major` **Tag:** `libdd-trace-stats-v9.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-data-pipeline **Next version:** `10.0.0` **Semver bump:** `major` **Tag:** `libdd-data-pipeline-v10.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-obfuscation`: ^7.0.0 → ^8.0.0 - `libdd-trace-stats`: ^8.0.0 → ^9.0.0 - `libdd-trace-utils`: ^11.0.0 → ^12.0.0 ### Commits - feat(trace-utils): add v1-native JSON log encoder brick (#2371) - chore: prepare crate for publishing (#2466) - refactor: migrate HTTP & networking deps to workspace level (phase 4bis) (#2350) - fix(trace-stats): read OTel HTTP names for the status and method dimensions (#2323) - fix(data-pipeline): pass obfuscation config to OTLP stats (#2444) - feat(data-pipeline): emit native trace export telemetry (#2338) - feat(data-pipeline): add fork-safe OTLP gRPC trace transport (#2273) - feat(data-pipeline)!: add agentless stats export (#2309) - feat(data-pipeline)!: Obfuscate v04 spans in agentless context (#2418) - feat(data-pipeline): add runtime-independent agentless sending (#2389) - feat(trace-utils)!: add from owned to SpanText (#2403) ## libdd-ipc **Next version:** `2.0.0` **Semver bump:** `major` **Tag:** `libdd-ipc-v2.0.0` ### ⚠️ major bump forced due to: - `libdd-common`: ^5.2.0 → ^6.0.0 - `libdd-trace-stats`: ^8.0.0 → ^9.0.0 ### Commits - fix(ipc): drop the signal feature from libdd-ipc (#2431) ## libdd-live-debugger **Next version:** `1.0.0` **Semver bump:** `major` **Tag:** `libdd-live-debugger-v1.0.0` **Warning:** this is an initial release. Please verify that the version and commits included are correct. [EX-3425]: https://datadoghq.atlassian.net/browse/EX-3425?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>

bwoebi requested review from a team as code owners August 26, 2026 12:23

github-actions Bot added the common label Aug 26, 2026

bwoebi changed the title ~~Add HTTPS_PROXY support for hyper_proxy~~ feat(common): add HTTPS_PROXY support for hyper_proxy Aug 26, 2026

bwoebi changed the title ~~feat(common): add HTTPS_PROXY support for hyper_proxy~~ feat(common): add HTTPS_PROXY support for hyper_backend Aug 26, 2026

chatgpt-codex-connector Bot reviewed Aug 26, 2026

View reviewed changes

Comment thread libdd-http-client/tests/hyper_proxy_test.rs

Comment thread libdd-common/src/connector/proxy.rs Outdated

Comment thread libdd-http-client/Cargo.toml

bwoebi changed the title ~~feat(common): add HTTPS_PROXY support for hyper_backend~~ feat(common)!: add HTTPS_PROXY support for hyper_backend Aug 26, 2026

paullegranddc reviewed Aug 26, 2026

View reviewed changes

Comment thread libdd-http-client/tests/hyper_proxy_test.rs Outdated

Comment thread libdd-common/src/connector/proxy.rs Outdated

github-actions Bot added the ci-build label Aug 26, 2026

bwoebi force-pushed the bob/hyper-proxy branch 2 times, most recently from 5edfdf8 to 0afb70f Compare August 26, 2026 18:36

bwoebi added 3 commits August 26, 2026 21:32

Refactor to allow proxying https

8de89ec

Don't make this https only

156a65e

bwoebi force-pushed the bob/hyper-proxy branch from 0afb70f to 156a65e Compare August 26, 2026 19:32

paullegranddc approved these changes Aug 26, 2026

View reviewed changes

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

gh-worker-dd-mergequeue-cf854d Bot merged commit a0f2872 into main Aug 26, 2026
95 checks passed

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

gh-worker-dd-mergequeue-cf854d Bot deleted the bob/hyper-proxy branch August 26, 2026 21:14

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

Navigation Menu

Repository navigation

feat(common)!: add HTTPS_PROXY support for hyper_backend - #2421

feat(common)!: add HTTPS_PROXY support for hyper_backend#2421
gh-worker-dd-mergequeue-cf854d[bot] merged 3 commits into
mainfrom
bob/hyper-proxy

bwoebi commented Aug 26, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

datadog-official Bot commented Aug 26, 2026 •

edited by datadog-prod-us1-5 Bot

Loading

Uh oh!

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

edited

Loading

Uh oh!

pr-commenter Bot commented Aug 26, 2026 •

edited

Loading

Explanation

More details about the CI and significant changes

Explanation

More details about the CI and significant changes

Uh oh!

paullegranddc commented Aug 26, 2026

Uh oh!

bwoebi commented Aug 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

Uh oh!

bwoebi commented Aug 26, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Aug 26, 2026 •

edited

Loading

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

bwoebi commented Aug 26, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

Uh oh!

Uh oh!

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

Uh oh!

Uh oh!

dd-octo-sts Bot commented Aug 26, 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 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Benchmarks

Comparison

Explanation

More details about the CI and significant changes

scenario:msgpack_encoder::v04

scenario:otlp/e2e_json/1x1000

scenario:otlp/encode_json/1x1000

scenario:otlp/encode_protobuf/1x1000

scenario:vec_map/as_deduped_map/already_deduped/16

scenario:vec_map/as_deduped_map/already_deduped/8

scenario:vec_map/as_deduped_map/needs_dedup_1_in_10/8

scenario:vec_map/as_deduped_map/needs_dedup_1_in_2/8

scenario:vec_map/as_deduped_map/needs_dedup_1_in_4/8

scenario:vec_map/contains_key/8

scenario:vec_map/dedup/dup_1_in_10/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/16

scenario:vec_map/get_miss/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/ 3782-8224-6310-005

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/resource_pattern_rule_matching/wall_time

scenario:datadog_sample_span/tag_rule_matching/wall_time

scenario:glob_matcher/ascii_exact_miss/wall_time

scenario:glob_matcher/ascii_wildcard_question_match/wall_time

scenario:glob_matcher/ascii_wildcard_star_match/wall_time

scenario:trace_buffer/4_senders/no_delay

scenario:write only interface

Candidate

Baseline

Uh oh!

paullegranddc commented Aug 26, 2026

Uh oh!

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

Uh oh!

Uh oh!

Uh oh!

Uh oh!

bwoebi commented Aug 26, 2026

Uh oh!

gh-worker-devflow-routing-ef8351 Bot commented Aug 26, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

datadog-official Bot commented Aug 26, 2026 •

edited by datadog-prod-us1-5 Bot

Loading

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

edited

Loading

pr-commenter Bot commented Aug 26, 2026 •

edited

Loading

bwoebi commented Aug 26, 2026 •

edited

Loading

gh-worker-devflow-routing-ef8351 Bot commented Aug 26, 2026 •

edited

Loading