An administrator integrates a web application with Application Insights to capture execution profiles using the Profiler tool. However, after the application starts, no telemetry data or traces are visible in the Azure portal.
Which of the following is the most likely cause of this issue?
- The Application Insights SDK is initialized in the application code, but the connection string has not been configured in the environment settings.Cevap
- BThe application is hosted on an Azure Functions Consumption plan, which does not support the execution requirements of the Profiler.
- CThe application's managed identity has not been granted GET permissions on the Key Vault secrets where the connection string is stored.
- DThe Kusto Query Language (KQL) queries used to check for the traces in the portal omit a time range filter, causing them to exceed scan limits.
Cevap
The Application Insights SDK is initialized in the application code, but the connection string has not been configured in the environment settings.
For Application Insights to collect and display telemetry data, the SDK must be provided with a valid connection string. If the connection string is missing or not configured in the application environment settings, the SDK cannot send any telemetry data (including Profiler traces) to the Azure portal.
Adım Adım Çözüm
Anahtar Kavram
Application Insights SDK Initialization and Connection String Configuration
Tahmini Süre:45s