Azure Kubernetes Service(AKS) Troubleshooting FAQs

Azure Kubernetes Service(AKS) Troubleshooting FAQs

Azure Kubernetes Service (AKS) monitor can be configured only if you have already added a Microsoft Azure monitor in Applications Manager.
Ensure that you have met all the prerequisites for the Microsoft Azure monitor before monitoring Azure Kubernetes Service in Applications Manager.

How to verify if all the prerequisites have been met?

  1. Ensure that the pre-requisites required to monitor AKS cluster in Applications Manager is met.
  2. Verify if you are able to connect to the AKS cluster with the credential used in Applications Manager to monitor the subscription.
    1. For troubleshooting errors while connecting to the AKS cluster, refer the troubleshooting errors section.
    2. Refer here to troubleshoot network problems in AKS clusters.
If the issue still persists, please reach out via mail to appmanager-support@manageengine.com with the below information:
  1. Latest Support Information File (SIF), ensure that 'print all logs' is enabled.
  2. Screenshot of the below mentioned information from prerequisites:
    1. Command: az --version (To login to Azure account) --> Sample Output (For windows 10): azure-cli/2.31.0 Python/3.8.9 Windows/10 exe/AMD64 prompt/off)
    2. Command: kubectl version --client (To connect to EKS cluster) --> Sample Output starts with: Client Version: v1.23.2
    3. Check if the Applications Manager installed user has permission to access installed kubectl/azure-cli by verifying prerequisites mentioned above.
    4. Screenshot of network configuration in Azure portal > Kubernetes services > Networking.
    5. If Microsoft Entra ID authentication is used out of the three supported modes, send the screenshot of the configuration of the user for the Kubernetes cluster.
      1. Sample screenshots can be found in the document at the bottom of the page.
    6. Connect to the cluster and execute the below commands and get the output:
      1. kubectl get nodes
      2. kubectl get pods -A


Possible Errors in AKS Monitor and their troubleshooting

Data collection is not performed as kubectl/azure-cli util is not found.

  1. Ensure that the Azure CLI and kubectl is installed in the Applications Manager installed server.
    1. Refer the prerequisites for the installation steps.
  2. Ensure the Applications Manager service logon user has the necessary permissions to access the kubectl/azure-cli utility 
    1. Open Services.msc
    2. Right click and open Properties of the service 'ManageEngine Applications Manager'.
    3. Go to Log On tab and select This account.
    4. Click Browse and select an admin user.
    5. Enter the Password and click on Apply.
    6. Now restart the AppManager service and then try polling the monitor.

Data collection has stopped. Unable to connect to AKS cluster endpoint via kubectl.

  1. Ensure the network connectivity of the Applications Manager installed server.

  2. Check the firewall configured for the AKS cluster and the firewall of Applications Manager server.

  3. If you are using a private AKS endpoint and you encounter this error, refer here to run kubectl commands using private endpoint access.

Timeout exceeded when executing kubectl command.

  1. Increase the timeout value. (The default and minimum value for timeout is 30 seconds). To increase the value, go to Azure Kubernetes Service monitor page, monitor actions -> Edit monitor -> give the appropriate value and update.

  2. Ensure your system has a stable network connectivity.

  3. Connect to the AKS cluster and run the following kubectl commands to get to know the approximate amount of time it takes to receive a response.

    1. kubectl get nodes

    2. kubectl get pods --all-namespaces

Unable to perform data collection as the Cluster is in Stopped state.

  1. We initiate data collection only when the AKS cluster is in RUNNING state.

    1. Possible states: RUNNING, STOPPED.


    2. If the cluster is in any other state (unless it is deleted), we will only update the "Cluster Information" group in "Overview" tab.

  2. To start data collection, go to Azure Portal -> Kubernetes Services -> Select the Cluster for which you want to start data collection -> click Start.

Error in configuring cluster to kubectl

  1. Ensure the prerequisites are completed properly. Get the screenshots for the same.
  2. Refer this troubleshooting document to run direct commands to connect the cluster and check if you are able to get the data. Provide the same inputs as provided in the Microsoft Azure monitor in Applications Manager. 

Unable to collect kubectl performance metrics. Reason: Command '{command}' not found

  1. Connect to the AKS cluster and run the command which is causing the issue in the machine where kubectl and Application Manager installed. Refer this troubleshooting document to connect the cluster to run the problematic command and send us the output.

Unable to collect some of the performance metrics. Reason {REASON}

  1. Ensure that you have met the pre-requisites particularly steps to enable container insights.
  2. Verify if Container Insights metrics are populated in Azure console only then Applications Manager can collect container insights metrics. 
  3. Steps to verify if the Container Insights metrics are populated in Azure console:
    Go to Azure portal -> Kubernetes Service -> Select the Cluster for which you have enabled container insights -> Monitoring tab in the left pane -> Metrics -> check if Namespaces available under Custom category -> click on the required Namespace(insights.container/nodes) -> choose the metric(cpuUsagePercentage) to see the data.
Applications Manager will be able to fetch the data for container insights only if it is populated in Azure console.


Frequently Asked Questions

How to bypass proxy for AKS Cluster FQDN?

  1. In Applications manager, navigate to Settings > Product settings > Proxy Server Settings.
  2. First verify if Proxy server has been configured in Applications Manager.
  3. If yes, to exclude kubectl from using proxy, navigate to Azure Kubernetes Service monitor page > Overview tab > Cluster information and get Cluster FQDN information. Give the endpoint information in the Do not use proxy for addresses beginning with field without protocol(http/https) 
Proxy is only supported from kubectl version 1.19 and above.

How to disable automatic alerts for a specific node condition?

Disable the specific condition by navigating to Settings > Performance Polling > Optimize Data Collection > Azure Kubernetes Service.



If a node is not in the ready state, its health will be automatically affected.



      New to M365 Manager Plus?
      New to M365 Manager Plus?
        New to RecoveryManager Plus?
        New to RecoveryManager Plus?
          New to Exchange Reporter Plus?
          New to Exchange Reporter Plus?
            New to SharePoint Manager Plus?
            New to SharePoint Manager Plus?
                See all integrations
                New to ADManager Plus?
                See all integrations
                New to ADManager Plus?

                  New to ADSelfService Plus?

                  Start your free trial
                  Start your free trial

                      Related Products