You are configuring telemetry for a C# application using the Application Insights SDK. You instantiate and initialize the telemetry client, but notice that no telemetry data is transmitted to Azure Monitor. You confirm that there are no runtime exceptions, compile errors, or network blockages.
Which of the following is the most likely cause of this behavior?
- The connection string was not configured on the telemetry configuration object.Cevap
- BThe instrumentation key was configured using the Azure Subscription ID instead of the Application Insights resource ID.
- CThe SDK was initialized without configuring a system-assigned managed identity for the application.
- DThe SDK automatically disables all telemetry tracking when the hosting environment is detected as local development.
Cevap
The connection string was not configured on the telemetry configuration object.
The correct option is correct because the Application Insights SDK requires a valid connection string to locate the ingestion endpoint and authenticate the payload. When the connection string is missing or empty, the SDK does not throw exceptions but silently fails to send any telemetry data.
Adım Adım Çözüm
Anahtar Kavram
Configuring Application Insights connection string to enable telemetry ingestion