AB#5828: AKS Autoinstrumentation Troubleshooting

Author: AmandaAZ

support/azure/azure-monitor/app-insights/telemetry/troubleshoot-missing-telemetry.md

@@ -0,0 +1,52 @@
+---
+title: Troubleshoot Missing Telemetry in Application Insights
+description: Helps troubleshoot telemetry problems with auto-instrumentation in Application Insights.
+ms.service: azure-monitor
+ms.custom: sap:Application Insights
+ms.date: 05/21/2025
+---
+# Troubleshoot missing telemetry in Azure Monitor Application Insights
+
+This article provides a step-by-step guide to troubleshoot issues when no data appears in a workspace-based Application Insights resource.
+
+## Prerequisites
+
+Ensure that the Kubernetes command-line tool (`kubectl`) is installed and configured.
+
+## Troubleshooting steps
+
+1. Confirm the pod is in the running state.
+
+2. Verify the deployment is instrumented
+
+3. 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"]}`
+
+4. If the annotation is present, the deployment is instrumented, and you should proceed to the next step. If the annotation isn't present, then the deployment isn't instrumented. In this case, restart the deployment by following these steps:
+
+    1. [Prepare your cluster](/azure/azure-monitor/app/kubernetes-codeless#prepare-a-cluster).
+    2. 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.
+    3. [Restart the deployment](/azure/azure-monitor/app/kubernetes-codeless#restart-deployment).
+
+5. Check for networking errors in the SDK log located in the pod's logs 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 into the container and test connectivity to the endpoint.
+
+    ```console
+    kubectl exec -ti customer-java-1-1234567890-abcde -- /bin/bash
+    ```
+
+    If connectivity can't be established, troubleshoot the network connectivity issue such as firewall or name resolution issues.
+
+[!INCLUDE [Azure Help Support](../../../../includes/azure-help-support.md)]

support/azure/azure-monitor/toc.yml

@@ -23,6 +23,8 @@ items:
       href: app-insights/telemetry/investigate-missing-telemetry.md
     - name: Troubleshoot auto-instrumentation issues
       href: app-insights/telemetry/auto-instrumentation-troubleshoot.md
+    - name: Troubleshoot missing telemetry
+      href: app-insights/telemetry/troubleshoot-missing-telemetry.md
     - name: Troubleshoot high data ingestion
       href: app-insights/telemetry/troubleshoot-high-data-ingestion.md
     - name: Application Insights classic SDK troubleshooting