Support OpenTelemetry deployment environment names

[tylfin]

What Does This Do

Maps the stable OpenTelemetry deployment.environment.name resource attribute to the Datadog environment while retaining deployment.environment as a legacy fallback. When both attributes are present, the stable name takes precedence.

Motivation

OpenTelemetry deprecated deployment.environment in favor of deployment.environment.name. Applications using the current semantic convention were not assigned the expected Datadog environment.

Additional Notes

Validated with focused configuration tests and Spotless checks.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the required type, component, and AI-generated labels
• Preserve compatibility with the deprecated resource attribute

[datadog-prod-us1-4]

More details

The change maps deployment.environment.name to the Datadog environment. It keeps deployment.environment as a fallback and removes both keys from generic tags.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

_{🤖 Datadog Autotest · Commit 65b75ba · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[datadog-prod-us1-4]

🎯 Code Coverage (details)
• Patch Coverage: 0.00%
• Overall Coverage: 58.37% (-0.43%)

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

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.83 s	14.69 s	[+0.1%; +1.9%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.59 s	13.76 s	[-2.0%; -0.4%] (maybe better)
startup:petclinic:appsec:Agent	17.40 s	16.83 s	[-0.9%; +7.6%] (no difference)
startup:petclinic:iast:Agent	17.35 s	17.21 s	[-3.7%; +5.3%] (no difference)
startup:petclinic:profiling:Agent	17.25 s	16.77 s	[-1.5%; +7.3%] (no difference)
startup:petclinic:sca:Agent	16.90 s	17.22 s	[-6.2%; +2.4%] (no difference)
startup:petclinic:tracing:Agent	16.16 s	16.23 s	[-6.2%; +5.4%] (unstable)

Commit: 7c2b26c3 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[zacharycmontoya]

Functionally, LGTM so we can understand either OTel convention for specifying the application environment. I'd love to get a Java reviewer to confirm the testing strategy

[mhlidd]

LGTM following an additional test case.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-27 19:27:42 UTC ℹ️ Start processing command /merge

---

2026-08-27 19:27:48 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-08-27 20:37:02 UTC ℹ️ MergeQueue: This merge request was merged