Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
This article provides a step-by-step guide to troubleshoot an issue where no telemetry data appears in a workspace-based Application Insights resource.
Prerequisites
Ensure that the Kubernetes command-line tool (kubectl
) is installed and configured.
Troubleshooting steps
Confirm the pod is running.
Verify the deployment is instrumented.
Check for the
monitor.azure.com/instrumentation
annotation on the deployment and its latest replica set.The annotation should be present with proper JSON in the following pattern:
{"crName": "crName1","crResourceVersion": "20177993","platforms":["Java"]}
If the annotation is present, the deployment is instrumented, and you should proceed to the next step. If the annotation isn't present, the deployment isn't instrumented. In this case, restart the deployment by following these steps:
- Prepare your cluster.
- Confirm the following things:
- The Instrumentation custom resource is in the correct namespace as the deployment.
- The Instrumentation custom resource contains the correct connection string and instrumentation platform.
- Restart the deployment.
Check for networking errors in the SDK log located in the pod's log volume: /var/log/applicationinsights.
For example, the following errors indicate a connectivity issue:
-
Ingestion endpoint could not be reached.
-
Error: getaddrinfo ENOTFOUND eastus2-3.in.applicationinsights.azure.com
-
getaddrinfo ENOTFOUND eastus2-3.in.applicationinsights.azure.com
If this type of error exists, sign in to the container and test connectivity to the endpoint:
kubectl exec -ti <pod-name> -- /bin/bash
If a connection can't be established, troubleshoot the network connectivity issue, such as firewall or name resolution issues.
-
Contact us for help
If you have questions or need help, create a support request, or ask Azure community support. You can also submit product feedback to Azure feedback community.