Application Insights does not recognize resource detected by Azure Container Apps detector as Azure resource

[hansmbakker]

Component

OpenTelemetry.Resources.Azure

Package Version

Package Name	Version
OpenTelemetry	1.9.0

Runtime Version

net8.0

Description

I’m using Aspire.NET which has support for OpenTelemetry export to Application Insights. It uses the AzureContainerAppsResourceDetector which enables some Container App properties to be correctly ingested in Application Insights – like its Application Map.

However, when inspecting a node’s Compute details, it says

We didn't detect any Azure resources connected to backend. If you know that this should be connected to an Azure resource, your current Application Insights SDK/Agent may not support this detection.”

I read Migrate from Application Insights .NET SDKs to Azure Monitor OpenTelemetry - Azure Monitor | Microsoft Learn and Application map in Azure Application Insights - Azure Monitor | Microsoft Learn but those pages do not give me any pointers.

Steps to Reproduce

Create a basic Aspire.NET app.
Run it in Container Apps
Send the opentelemetry to Application Insights

Expected Result

The container app is recognized as an Azure resource in the Application Insights Application Map. It is possible to see the compute details when selecting the node.

Actual Result

The container app is detected but only marked with its app name. Azure Application insights does not recognize what Azure resource it belongs to. The Compute blade on the Application Map is empty for the given node.

Additional Context

This is also sent to OTel@microsoft.com.

The detector sets

• service.name to the name of the Container App
• service.version to the revision of the Container App
• service.instance.id to the replica name of the Container App

but this might not be enough. Maybe Application Insights is expecting a full resource id (incl. subscription id and resource group name) in one of these properties or another property? The documentation at Understand cloud role names and nodes does not clearly state that this would be required, though.