Skip to content

Commit 2a77aa8

Browse files
committed
Update functions-monitoring.md to recommend Azure Monitor OpenTelemetry Exporter and clarify connection string requirements
1 parent 2443429 commit 2a77aa8

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

articles/azure-functions/functions-monitoring.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,8 @@ Azure Functions generates telemetry data from both the Functions host process an
3333

3434
> [!IMPORTANT]
3535
> For new and existing applications, the recommended approach is to use the [Azure Monitor OpenTelemetry Exporter](opentelemetry-howto.md) to send telemetry to Application Insights. If you're currently using a classic Application Insights SDK to customize your exported telemetry, plan to migrate to OpenTelemetry for long-term support and access to the latest observability capabilities. The classic Application Insights SDKs won't receive new feature updates. OpenTelemetry isn't supported for [C# in-process apps](functions-dotnet-class-library.md).
36+
>
37+
> The Azure Monitor OpenTelemetry Exporter requires an Application Insights connection string (`APPLICATIONINSIGHTS_CONNECTION_STRING`) and doesn't support the use of an instrumentation key.
3638
3739
To learn how to configure OpenTelemetry in your function app, see [Use OpenTelemetry with Azure Functions](opentelemetry-howto.md).
3840

0 commit comments

Comments
 (0)