Understanding Azure Function Observability with OpenTelemetry DotNet Edition
Blog post from New Relic
New Relic observes a growing trend of customers adopting OpenTelemetry for observability, particularly in serverless environments like Azure Functions. To enhance visibility, the guide details how to instrument DotNet Azure Functions with OpenTelemetry, emphasizing the separation of the Azure Functions Host, which manages the function lifecycle, from the .NET Isolated Worker process, where the OpenTelemetry SDK is configured. It highlights the importance of configuring the telemetryMode in the host.json file to switch from Application Insights to OpenTelemetry, allowing for comprehensive data collection from both the host and worker processes. The guide further explains how to set up OpenTelemetry in the application's worker process using specific packages and the significance of properly configuring data exporters and sampling. New Relic's support for OpenTelemetry includes automatic metric normalization and enhanced APM UI experiences, ensuring that users can monitor and analyze their applications effectively.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| OpenTelemetry | 47 | 609 | 94 | 39 | +191% |
| Observability | 8 | 2,534 | 521 | 146 | +9% |
| Serverless | 1 | 701 | 157 | 77 | -20% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.