But wait, there’s more—Microsoft envisions expanding OpenTelemetry far beyond Logic Apps and Functions. They aim to streamline observability across their entire cloud infrastructure. Azure provides a diverse toolkit for managing telemetry data seamlessly, whether it’s on Azure Monitor or exploring locally.
Microsoft has officially announced the enhanced support for OpenTelemetry in Azure Logic Apps (Standard and Hybrid) and Azure Functions (Public Preview).
Thrilled about the new advanced Azure Functions support in Aspire. We’re moving towards establishing open telemetry as the real deal universally and ensuring seamless local development with our top-notch emulators.
For those diving deep into Azure Logic Apps, particularly in hybrid or on-premises configurations, along with the Azure Functions team, OTel is a groundbreaking solution for diagnostic expertise. Wave goodbye to the standard Application Insights and embrace this elevated approach.
Renowned figure in Azure realm, Microsoft’s David Fowler, recently shared on Twitter:
The essence of this grand strategy includes:
OpenTelemetry (OTel), a top-tier open-source observability framework from the Cloud Native Computing Foundation (CNCF), proves vital in managing logs, metrics, and traces. It eliminates the complexity of vendor-specific tracking and embraces compatibility with various observability platforms like Azure Monitor, Grafana Tempo, and Jaeger.
Currently, OpenTelemetry in Logic Apps supports HTTP, Service Bus, and Event Hub triggers for dialogue—metrics integration pending. With Azure Functions, OpenTelemetry is under testing, with a few intricacies such as the Azure portal struggling to offer log streaming or trace insights post-OTel migration. Kudos to that!
To integrate OpenTelemetry into Azure Logic Apps (Standard and Hybrid) and Azure Functions, you will need to make adjustments in the host.json file to switch to “telemetryMode”: “OpenTelemetry” and configure your app settings for the OTLP exporter endpoint (OTEL_EXPORTER_OTLP_ENDPOINT) and any additional headers (OTEL_EXPORTER_OTLP_HEADERS). You can begin this process with Visual Studio Code or, for the daring, head straight to the Azure Portal and adapt it to your hosting environment (Workflow Standard Plan, App Service Environment v3, or Hybrid containers).
