Add stable OTel environment attribute mapping

[bm1549]

What does this PR do?

Maps deployment.environment.name from OTEL_RESOURCE_ATTRIBUTES to the Datadog environment. The stable attribute takes precedence over the legacy deployment.environment fallback, and DD_ENV still wins.

OpenTelemetry Logs and Metrics emit the resolved environment as deployment.environment.name and no longer emit deployment.environment.

The shared signal configuration declares its settings type and explicitly selects Logs or Metrics settings, removing its steep:ignore suppressions.

Motivation:

OpenTelemetry stabilized the deployment environment semantic convention under deployment.environment.name.

Related PRs:

• test: cover OTel deployment environment mapping [golang@brian.marks/otel-deployment-environment-name][dotnet@brian.marks/otel-deployment-environment-name][ruby@brian.marks/otel-deployment-environment-name][php@brian.marks/otel-deployment-environment-name][nodejs@brian.marks/otel-deployment-environment-name][rust@brian.marks/otel-deployment-environment-name] system-tests#7613
• fix(config): support stable OTel deployment environment dd-trace-go#5285
• Support stable OTel deployment environment attribute dd-trace-dotnet#9150
• Add stable OTel environment attribute mapping #6261
• fix: support stable OTel deployment environment dd-trace-php#4148
• fix(config): prefer stable OTel deployment environment dd-trace-js#10050
• fix(config): map OTel deployment environment dd-trace-rs#300
• Support OpenTelemetry deployment environment names dd-trace-java#12324
• fix(config): support OTel deployment environment name dd-trace-py#19901

Change log entry

Yes. unreleased/20260930140422.json records the Logs and Metrics output-key change and the legacy input fallback.

Additional Notes:

I read and checked the AI-assisted changes.

How to test the change?

• Ruby 2.5 and 4.0: 9 focused deployment environment settings examples, 0 failures
• Ruby 2.6: full OpenTelemetry task, 254 examples, 0 failures, 65 pending for unsupported signals
• Ruby 4.0: full OpenTelemetry task, 254 examples, 0 failures
• Changelog schema, Vale, and rendered-output checks
• StandardRB and RuboCop, 1,994 files inspected with no offenses
• Steep, no type errors

[datadog-prod-us1-5]

✅ All CI checks and tests passed.

🎉 All green!

🧪 All tests passed
❄️ No new flaky tests detected

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 90.54% (-0.01%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 82a7190 | Docs | View more details | Give us feedback!}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-01T22:54:10.382405Z	0759282	Draft marked ready
🔒 Security Review	✅ Completed 2026-09-01T22:53:42.563641Z	0759282	Draft marked ready

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 07592829bb

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

[dd-octo-sts]

Typing analysis

Note: Ignored files are excluded from the next sections.

steep:ignore comments

This PR clears 8 steep:ignore comments.

steep:ignore comments (+0-8)

✅ Cleared:

lib/datadog/opentelemetry/signal_configuration.rb:15
lib/datadog/opentelemetry/signal_configuration.rb:25
lib/datadog/opentelemetry/signal_configuration.rb:26
lib/datadog/opentelemetry/signal_configuration.rb:27
lib/datadog/opentelemetry/signal_configuration.rb:29
lib/datadog/opentelemetry/signal_configuration.rb:31
lib/datadog/opentelemetry/signal_configuration.rb:44
lib/datadog/opentelemetry/signal_configuration.rb:46

[pr-commenter]

Benchmarks

Benchmark execution time: 2026-09-10 16:04:36

Comparing candidate commit b9a3a6a in PR branch brian.marks/otel-deployment-environment-name with baseline commit c067392 in branch master.

📊 Benchmarking dashboard

Found 0 performance improvements and 0 performance regressions! Performance is the same for 48 metrics, 1 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 ----------------------------------'

Unstable benchmarks

These benchmarks have a confidence interval too wide to call a change; treat them as noise rather than signal.

scenario:tracing - Tracing.continue_trace!

• unstable throughput [-2131.009op/s; +1738.402op/s] or [-5.517%; +4.501%]

[vpellan]

LGTM after applying the suggestions left by @y9v