How to Monitor the Azure Kubernetes Service Cluster Using eG Enterprise?

To monitor the Azure Kubernetes Service cluster using eG Enterprise, you need to first manage it.

eG Enterprise does not automatically discover the Azure Kubernetes Service cluster. To manage the cluster therefore, you need to manually add it to the eG Enterprise system using the eG admin interface. For this, follow the steps below:

  1. Login to the eG admin interface.

  2. Figure 1 then appears prompting you to pick what you want to monitor. Select Kubernetes and Containers from Figure 1.

    Choosing to Monitor Kubernetes / OpenShift

    Figure 1 : Choosing Kubernetes and Containers option

  3. eG Enterprise monitors Azure Kubernetes Service clusters in an agentless manner. To monitor the applications running on its containers, eG Enterprise recommends container agents as shown in Figure 2. Select Kubernetes, Rancher, OpenShift, EKS, AKS, Tanzu, Google from Figure 2.

    Figure 2 : Choosing Container Agent option

  4. This will invoke Figure 3. Select Kubernetes Cluster from Selective Monitoring section.

    Figure 3 : Choosing Kubernetes Cluster option

  5. This will invoke Figure 4. Select Azure Kubernetes Service as container orchestration type.

    Figure 4 : Choosing Azure Kubernetes Service

  6. This will invoke Figure 5, using which you can configure the details of the Azure Kubernetes Service cluster you want to monitor.

    Adding Kubernetes/OpenShift Cluster

    Figure 5 : Adding an Azure Kubernetes Service cluster

  7. In Figure 5, specify the following:

    • Provide a unique NICK NAME for the Azure Kubernetes Service cluster you want to monitor.

    • Specify the PORT at which the cluster listens. The default port is 6443.
    • The eG agent requires an authentication bearer token to access the Kubernetes API, run API commands on the cluster, and pull metrics of interest. The steps for generating this token have been detailed in How Does eG Enterprise Monitor Azure Kubernetes Service Cluster? You will also find these steps displayed in the right panel of Figure 5. Once you generate a token by following the displayed (or documented) steps, copy the token and paste it against AUTHENTICATION TOKEN in Figure 5.
    • Specify the IP address of the Kubernetes API against LOAD BALANCER / MASTER NODE IP text box of Figure 5. To determine the IP address of the Kubernetes API, follow the steps detailed in the How Does eG Enterprise Monitor Azure Kubernetes Service Cluster? topic.
    • Select the remote agent from the REMOTE AGENT list.

    • Finally, click the Update button in Figure 5 to add the component to eG Enterprise.