TelemetryConfigration.Active deprecated

[skjelmo]

TelemetryConfigration.Active is deprecated with ApplicationInsights SDK 2.11-beta1 as described here, so the first example under using config file
should maybe reflect that?

Could be done similar to how TelemetryProcessorChainBuilder is described here

---

Document Details

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

• ID: b189efce-ce4e-f8f8-ecf8-8803a18f9b65
• Version Independent ID: aec54012-dae3-ce18-0f8c-30749c46a79c
• Content: Azure Application Insights for Console Applications
• Content Source: articles/azure-monitor/app/console.md
• Service: application-insights
• GitHub Login: @mrbullwinkle
• Microsoft Alias: mbullwin

[SamaraSoucy-MSFT]

@eivinskr Thank you for your feedback. I will investigate and get back to your shortly.

[SamaraSoucy-MSFT]

@eivenskr TelemetryConfigration.Active is being deprecated for .NET Core only. As is noted in the doc, using config files is not supported in .NET Core.

In the doc for .NET Core there is also a note that TelemetryConfiguration.Active is not supported for Core.

I will now proceed to close this thread. Please tag me if you need to discuss this further.

[skjelmo]

Ahh, I have two things I still find weird if you don't mind discussing it @SamaraSoucy-MSFT.

• It was posted in the .NET Github repo for Application Insights, not the .NET Core Github repo.
• After describing how to configure AppInsights for ASP.NET Core and Azure functions it says:

If you have other kind of application where you configure TelemetryConfiguration yourself - do not use TelemetryConfiguration.Active singleton

But as you mention, I don't get why that should be a problem if TelemetryConfiguration.Active is only being deprecated in .Net Core.

[SamaraSoucy-MSFT]

The Application Insights package is used in both Framework and Core. The .NET Core SDK has it as a dependency.

TelemetryConfiguration.Active is a backup for when you don't have dependency injection available. Think of it as a default implementation that can be used in simple scenarios. In the doc example, Active avoids the complexity of setting up DI in .NET Framework. DI is built into .NET Core so there is no need to deal with the issues that can come with the Active singleton.

If you are setting up the configuration somewhere else, like through DI, using Active creates a second instance of the configuration and can cause conflicts. This is exactly the problem that is happening in Core apps.

[skjelmo]

Thank you for clearing up the confusion!