Application Insights Connection String Missing¶

Use this playbook when traffic reaches the app but expected traces, requests, or logs do not appear in Application Insights.

Symptom¶

• The app responds successfully, but requests, traces, or exceptions stay empty in Application Insights.
• Operators expect telemetry because the environment or app was recently configured for Application Insights.
• A deployment changed environment variables or secrets and telemetry stopped without affecting the primary request path.

Possible Causes¶

• No valid Application Insights connection string is configured for the telemetry path being used.
• The environment telemetry destination exists, but the app itself is not instrumented to emit the signal you expect.
• The app uses a secret reference or environment variable name that no longer resolves correctly.
• Operators are checking the wrong Application Insights resource.
• Telemetry was enabled at the environment level, but no new traffic was generated after the change.

Diagnosis Steps¶

flowchart TD
    A[Notice missing telemetry in Application Insights] --> B[Confirm traffic still reaches the app]
    B --> C[Inspect environment telemetry configuration]
    C --> D[Inspect app environment variables and secret references]
    D --> E[Generate fresh traffic]
    E --> F[Query requests and traces in the intended Application Insights resource]
    F --> G{Telemetry appears?}
    G -->|Yes| H[Classify as propagation or stale-query issue]
    G -->|No| I[Fix connection string or instrumentation path]

1. Confirm the environment telemetry configuration.

az containerapp env telemetry app-insights show \
    --name "$CONTAINER_ENV" \
    --resource-group "$RG" \
    --output json

1. Inspect the container app environment variable definitions and secret references.

az containerapp show \
    --name "$APP_NAME" \
    --resource-group "$RG" \
    --query "properties.template.containers[0].env[].{name:name,secretRef:secretRef}" \
    --output json

1. Verify that you are querying the intended Application Insights component.

az monitor app-insights component show \
    --app "$APPINSIGHTS_NAME" \
    --resource-group "$RG" \
    --query "{appId:appId,name:name,location:location}" \
    --output json

1. Generate fresh traffic after configuration changes.

curl --silent --show-error "$APP_URL"

1. Query recent request and trace volume.

requests
| where timestamp > ago(30m)
| summarize requestCount=count() by cloud_RoleName
| order by requestCount desc

traces
| where timestamp > ago(30m)
| summarize traceCount=count() by cloud_RoleName
| order by traceCount desc

1. If you prefer a CLI verification path, run the Application Insights query directly.

az monitor app-insights query \
    --app "$APPINSIGHTS_NAME" \
    --resource-group "$RG" \
    --analytics-query "requests | where timestamp > ago(30m) | summarize count() by cloud_RoleName" \
    --output table

Resolution¶

1. Configure the correct connection string on the telemetry path you actually use.

az containerapp env telemetry app-insights set \
    --name "$CONTAINER_ENV" \
    --resource-group "$RG" \
    --connection-string "$APPLICATIONINSIGHTS_CONNECTION_STRING" \
    --enable-open-telemetry-traces true \
    --enable-open-telemetry-logs true

1. If the application uses the Application Insights SDK directly, restore the APPLICATIONINSIGHTS_CONNECTION_STRING environment variable or its referenced secret in the app definition.
2. Generate fresh requests after the change and re-query requests and traces over the last 15 to 30 minutes.
3. If telemetry still does not appear, treat the issue as an instrumentation-path problem rather than only a missing connection string problem.

Prevention¶

• Store the connection string in a secret-backed workflow instead of hard-coding it in ad hoc commands.
• After each deployment, validate both the configuration state and the presence of fresh telemetry.
• Document whether the workload depends on environment-level OpenTelemetry, SDK-based instrumentation, or both.
• Keep one saved query for requests and one for traces so missing telemetry is detected early.
• Avoid sharing raw CLI output that could include literal environment variable values or telemetry configuration details.

See Also¶

• Application Insights Connection String Missing Lab
• Observability Tracing Lab
• Diagnostic Settings Missing
• Log Analytics Ingestion Gap

Sources¶

• Collect and read OpenTelemetry data in Azure Container Apps
• Observability in Azure Container Apps
• Connection strings in Application Insights