Support stable OTel deployment environment attribute - #9150
Conversation
BenchmarksBenchmark execution time: 2026-09-17 21:10:15 Comparing candidate commit 08968bc in PR branch Found 0 performance improvements and 11 performance regressions! Performance is the same for 61 metrics, 0 unstable metrics, 72 known flaky benchmarks, 54 flaky benchmarks without significant changes.
|
Execution-Time Benchmarks Report ⏱️Execution-time results for samples comparing This PR (9150) and master. ✅ No regressions detected |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
There are going to be some small merge conflicts so let's wait to include this after the next release, when we'll re-incorporate Milan's tracestate work |
…t we prefer deployment.environment.name
…te so that it falls back to the legacy deployment.environment resource attribute
2902519 to
08968bc
Compare
zacharycmontoya
left a comment
There was a problem hiding this comment.
Approving the improvement, but I also added a commit to this PR so does it count?
Summary of changes
Map
deployment.environment.nameto the Datadog environment. Keepdeployment.environmentas a fallback, and keepDD_ENVas the highest-precedence source.Reason for change
OpenTelemetry stabilized the deployment environment semantic convention under
deployment.environment.name.Related PRs:
Implementation details
The resource attribute mapper tracks the stable and legacy values separately, then chooses the stable value regardless of input order. It removes both source aliases after promotion and leaves unrelated attributes alone.
Test coverage
Five focused mapping cases and 182 adjacent configuration tests passed locally. Formatting checks also passed.
Other details
None.