fix(tracing): handle env var values containing =

[KowalskiThomas]

Description

Previously, we would split without a component count limit, meaning if we had ENV=something=else an exception would be raised and we would fail to process it. Added a limit of 2 components so that we get the env variable name and discard all the rest, making it safer.

On top of that, the PR adds support for env var names containing digits -- those didn't use to match the regex and were thus ignored from scrubbing.

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-05-18 15:04:52

Comparing candidate commit 6353bcd in PR branch kowalski/fix-tracing-handle-env-var-values-containing with baseline commit 7ec0ac7 in branch main.

Found 0 performance improvements and 4 performance regressions! Performance is the same for 591 metrics, 10 unstable metrics.

scenario:iastaspects-stringio_aspect

• 🟥 execution_time [+547.378µs; +584.518µs] or [+13.972%; +14.920%]

scenario:iastaspectsospath-ospathbasename_aspect

• 🟥 execution_time [+100.876µs; +107.477µs] or [+23.287%; +24.811%]

scenario:span-start

• 🟥 execution_time [+1.477ms; +1.623ms] or [+9.489%; +10.431%]

scenario:telemetryaddmetric-1-count-metric-1-times

• 🟥 execution_time [+235.548ns; +269.327ns] or [+11.227%; +12.837%]

[cit-pr-commenter-54b7da]

Codeowners resolved as

ddtrace/contrib/internal/subprocess/patch.py                            @DataDog/asm-python
releasenotes/notes/fix-subprocess-env-var-multi-equals-c8f20ac468cdd905.yaml  @DataDog/apm-python
tests/contrib/subprocess/test_subprocess.py                             @DataDog/asm-python

[datadog-datadog-prod-us1-2]

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

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

[KowalskiThomas]

/merge -f --reason "MQ failing for unrelated reasons (benchmark SLOs)"

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-05-21 12:26:27 UTC ℹ️ Start processing command /merge -f --reason "MQ failing for unrelated reasons (benchmark SLOs)"

---

2026-05-21 12:26:33 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in main is approximately 0s (p90).

---

2026-05-21 12:26:45 UTC ℹ️ MergeQueue: This merge request was merged

Warning

This change was merged without running any pre merge CI checks

Reason: MQ failing for unrelated reasons (benchmark SLOs)