[FEATURE]: DD_METRICS_OTEL_ENABLED bridge should route via DogStatsD named pipe on Azure App Service

[Christopher-McEwen]

Framework or Library Name

No response

Library Type

No response

Library Version(s)

No response

Describe the feature you'd like

When running on Azure App Service via the Datadog site extension, DD_METRICS_OTEL_ENABLED=true has no effect. The existing bridge should route measurements through the DogStatsD named pipe that the extension already provides, rather than assuming an OTLP endpoint is available on localhost.

Is your feature request related to a problem?

No response

Describe alternatives you've considered

No response

Additional context

No response

[andrewlock]

Hi @Christopher-McEwen the DD_METRICS_OTEL_ENABLED feature is explicitly about sending runtime metrics to an OTLP endpoint. Can I check what it is you're trying to achieve? you can enable standard runtime metrics through DogStatsD using DD_RUNTIME_METRICS_ENABLED=1

[Christopher-McEwen]

Many libraries such as MassTransit, Azure Cosmos SDK, etc. now emit metrics via OTEL meters, and we'd love to forward these to Datadog without managing a separate collector or agent sidecar.

On Azure App Service this isn't currently possible with DD_METRICS_OTEL_ENABLED=true, because the bridge assumes an OTLP endpoint is available locally rather than routing via the named pipe that the site extension already provides.

For comparison, DD_TRACE_OTEL_ENABLED=true works correctly on AAS. OTEL spans are bridged and forwarded over the named pipe. It would be great to see the same parity for metrics.

[andrewlock]

Noted, thanks for the details! Yes, that scenario isn't currently supported, but it definitely seems reasonable. Could you please submit a feature request via Datadog Support for this using the New Issue button above? It will help with getting it prioritised, thanks!