Azure App Insights broken when using ServiceDefaults

[natelaff]

Well #4322 was closed, but I still have an issue with app insights not pushing in my app when running on Azure.

I added Orchestrator support to my app and all seemed great. But when running on Azure App Services, I noticed app insights were no longer pushing.

var builder = WebApplication.CreateBuilder(args);
builder.AddServiceDefaults();

var config = builder.Configuration;

builder.Services.AddApplicationInsightsTelemetry(options => {
    options.DeveloperMode = builder.Environment.IsDevelopment();
    options.ConnectionString = config["APPLICATIONINSIGHTS_CONNECTION_STRING"];

The issue seems to stem from the call to

builder.ConfigureOpenTelemetry();

in the ServiceDefaults. If i comment that out and run in Azure, my insights start working again.

[davidfowl]

cc @samsp-msft

[samsp-msft]

It looks like you are mixing the classic Application Insights SDK and OpenTelemetry. Aspire is built using OpenTelemetry and the OTel based exporters to AzureMonitor/Application Insights. The call to ServiceDefaults is setting up OpenTelemetry.

To use Application Insights with Aspire, please use either Azure Monitor Distro or Azure monitor exporter. The former is a wrapper around the latter that provides good defaults and extensions to provide the best experience.

https://learn.microsoft.com/en-us/azure/azure-monitor/app/opentelemetry-enable?tabs=aspnetcore#enable-azure-monitor-opentelemetry-for-net-nodejs-python-and-java-applications
https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/application-insights

[natelaff]

Ok, I will look into those thanks. The issue in my opinion here is adding App Insights telemetry to the project via right click gives you this code. Adding Aspire orchestration which then adds the Service defaults gives you conflicting code. Something to consider ;)

[davidfowl]

@samsp-msft This is worth a documentation update.

[DGAISmith]

Is there a use case in this scenario where you would want to use AddApplicationInsightsTelemetry when deployed to azure, but ConfigureOpenTelemetry when running locally. Thinking mainly about when existing services which already use AppInsights have Aspire support added to them, and a developer might want to use OTEL and the Aspire Dashboard when running locally, but retain the existing AppInsights when deployed (via whatever existing deployment mechanism the service already has in place)

[davidfowl]

Absolutely! Though there are several ways to do that. OpenTelemetry has a concept of exporters and there's one for azure monitor (that replaces calls to AddApplicationInsightsTelemetry). So you're funneling everything through a single system.

If you can't upgrade to the new APIs for some reason, it should be possible to make them work side by side or only in dev and only when deployed.