Azure-docs: ApplicationInsights warning - clarification

[oatsoda]

Do not add AddApplicationInsightsTelemetry() to the services collection as it registers services that conflict with services provided by the environment.

Can this be clarified further? I added a dependency to my code on TelemetryClient but without adding AddApplicationInsightsTelemetry() the injected instance of TelemetryClient was null.

If I add AddApplicationInsightsTelemetry() to my FunctionsStartup class - what exactly is it breaking that the Warning is talking about?

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 5786402e-9d88-5de0-607a-1c2a143af006
• Version Independent ID: 15368d1c-b22e-7eb2-413f-cc0d41d2b909
• Content: Use dependency injection in .NET Azure Functions
• Content Source: articles/azure-functions/functions-dotnet-dependency-injection.md
• Service: azure-functions
• GitHub Login: @craigshoemaker
• Microsoft Alias: cshoe

[mike-urnun-msft]

@oatsoda Thank you for your feedback! We will review and update as appropriate.

[PramodValavala-MSFT]

@oatsoda The functions runtime already initializes application insights and uses the same for logging/metrics in its own code.

The idea here is to not re-initialize the same and instead use the existing services. If you require, your own TelemetryClient object, you should be able to create one from the injected TelemetryConfiguration as shown in this sample.

[PramodValavala-MSFT]

@oatsoda Just following up here... Hope my previous comment clears things up.

[PramodValavala-MSFT]

@oatsoda Hope my previous comment clears things up.

Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

[oatsoda]

@PramodValavala-MSFT Thanks - yes, it worked perfectly. I am adding AddApplicationInsightsTelemetry() to my startup when running locally in development, but not in Azure.

Adding the dependency on TelemetryConfiguration instead of TelemetryClient works as expected.

Thanks

[craigshoemaker]

I added a link to the sample that @PramodValavala-MSFT suggested in the warning box to make it more clear for others that want to do the same.