fix(otel): supress invalid env not supported warnings

[mabdinur]

Description

Adds OTEL_METRIC_EXPORT_TIMEOUT, OTEL_OTLP_HEADERS, OTEL_OTLP_PROTOCOL, OTEL_OTLP_TIMEOUT, and OTEL_EXPORTER_OTLP_METRICS_TEMPORALITY_PREFERENCE to SUPPORTED_OTEL_ENV_VARS in ddtrace/internal/settings/_otel_remapper.py. These are valid OpenTelemetry SDK variables listed in supported-configurations.json but were missing from the allowlist, causing an inaccurate "OpenTelemetry configuration ... is not supported by Datadog" warning at startup.

Testing

Existing OTel remapper/telemetry validation tests cover the allowlist path; no behavior change beyond suppressing the false-positive warning for these five variables.

Risks

None. Allowlist-only change — no remapping logic, defaults, or public API are affected.

Additional Notes

Audited every OTEL_* key in supported-configurations.json against SUPPORTED_OTEL_ENV_VARS and ENV_VAR_MAPPINGS; all entries are now accounted for.

[cit-pr-commenter-54b7da]

Codeowners resolved as

ddtrace/internal/settings/_otel_remapper.py                             @DataDog/apm-sdk-capabilities-python
releasenotes/notes/add-otel-configs-to-allowlist-bcf2be5c9ed79b61.yaml  @DataDog/apm-python

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 55427b449f

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

[chatgpt-codex-connector]

Don't suppress warnings for ignored OTEL_OTLP_ variables*

When a user sets OTEL_OTLP_PROTOCOL, OTEL_OTLP_HEADERS, or OTEL_OTLP_TIMEOUT, validate_otel_envs() now treats it as supported because it is in this allowlist, but the exporter config only reads the OTEL_EXPORTER_OTLP_* and signal-specific names. That makes these unsupported/typoed variables silently ignored instead of emitting the unsupported warning this allowlist controls; either wire them as aliases or keep warning on them.

Useful? React with 👍 / 👎.

[datadog-datadog-prod-us1]

 

✨ Fix all issues with BitsAI

⚠️ Warnings

🚦 8 Pipeline jobs failed

DataDog/apm-reliability/dd-trace-py | build linux serverless: [arm64, cp315-cp315, v113741589-d2b8243-musllinux_1_2_aarch64, 1]     

🔧 Fix in code (Fix with Cursor).

AssertionError: Failed with DD_IAST_ENABLED=0: 1

DataDog/apm-reliability/dd-trace-py | build linux: [arm64, cp315-cp315, v113741589-d2b8243-musllinux_1_2_aarch64]     

🔧 Fix in code (Fix with Cursor).

AssertionError: Failed with DD_IAST_ENABLED=0: 1

DataDog/apm-reliability/dd-trace-py | build linux serverless: [amd64, cp315-cp315, v113741238-d2b8243-manylinux2014_x86_64, 1]     

🛟 This job is unlikely to succeed on retry. Please review your pipeline configuration.

NotImplementedError: This version of CPython is not supported yet

View all 8 failed jobs.

ℹ️ Info

No other issues found (see more)

🧪 All tests passed
❄️ No new flaky tests detected

Useful? React with 👍 / 👎

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