You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run a Node.js app on Azure Container Apps with @azure/monitor-opentelemetry 1.20.1 and tried moving to @microsoft/opentelemetry 1.5.0, as the Azure Monitor docs now recommend. With default settings, two things differ on Container Apps:
The platform isn't detected: no cloud.platform or Container Apps attributes. @azure/monitor-opentelemetry includes azureContainerAppsDetector since 1.20.0.
The exporter's SDK-stats metadata lookup (GET http://169.254.169.254/metadata/instance/compute?api-version=2017-12-01) is exported as a failed dependency plus an ECONNREFUSED exception on each start (Container Apps has no IMDS). The same exporter version (1.0.0-beta.46) under @azure/monitor-opentelemetry 1.20.1 doesn't export it.
Evidence (our app's container image, Node.js 26.13, ESM with import-in-the-middle's synchronous hook; Container Apps conditions as measured on our live app: the six CONTAINER_APP_* variables set, IMDS refusing connections)
Distro
Settings
cloud.platform
Failed IMDS dependency + exception per start
@azure/monitor-opentelemetry 1.20.1
defaults
azure.container_apps
none
@microsoft/opentelemetry 1.5.0
defaults
not set
1 + 1
same
APPLICATIONINSIGHTS_STATSBEAT_DISABLED or …_STATSBEAT_DISABLED_ALL
Could the distro include azureContainerAppsDetector by default, and keep the SDK-stats metadata lookup out of exported telemetry on Container Apps, matching @azure/monitor-opentelemetry?
Alternatives Considered
The last two rows above work as workarounds. Neither blocks us, but we'd rather not turn SDK stats off or carry our own detector wiring, so for now we're staying on @azure/monitor-opentelemetry.
Activity
github-actions commentedon Nov 2, 2026
cc Hector Hernandez (@hectorhdzg) Jackson Weber (@JacksonWeber) Leighton Chen (@lzchen) Nev (@MSNev) Radhika Gupta (@rads-1996) Jeremy Voss (@jeremydvoss)