"Understanding the architecture is key to a smooth setup. To simplify the process, consider your function app as having two distinct components: Azure Functions Host, which handles triggers and manages the function lifecycle, and the Worker process, where your application code resides running in a separate process with the preloaded OpenTelemetry SDK."
"To enable OpenTelemetry output from your Functions host, regardless of the language, you must update the host.json file in your project root by adding the telemetryMode element set to OpenTelemetry to the root collection configuration."
"This guide was created because even though Azure's official OpenTelemetry for functions is in preview, current guidance wasn't available, especially around newer SDK configurations and ECMAScript Modules compilation, with many existing examples not covering practices required for SDK 2.x migration."
OpenTelemetry integration with Azure Functions requires understanding the architecture: the Azure Functions Host handles triggers and lifecycle management with built-in Application Insights telemetry, while the worker process runs application code where the OpenTelemetry SDK operates. Enable OpenTelemetry by adding telemetryMode to host.json configuration. Install necessary npm packages including Azure Functions OpenTelemetry instrumentation and OpenTelemetry auto-instrumentations for Node.js. This guide addresses the gap in current documentation for SDK 2.x migration and ESM compilation practices, providing updated configuration guidance beyond legacy CommonJS approaches and preview-stage Azure resources.
Read at New Relic
Unable to calculate read time
Collection
[
|
...
]