How to Monitor Kubernetes Using Zabbix, Part 2

This is the second installment in our series of videos showing how to monitor Kubernetes (and cloud-native applications) with Zabbix. Throughout the three-part series, we are reviewing key topics, including:

✅ How to install the necessary components to monitor a cluster with Zabbix
🔹 Understanding the metrics generated within Zabbix
🔹 Exploiting the Prometheus endpoints exposed by applications to monitor application-specific metrics

➡️ Understanding the metrics generated within Zabbix
In our previous video, we installed the Zabbix Agent Helm Chart and set up official Kubernetes templates to monitor a cluster in Zabbix. In this edition, part 2 of how to monitor Kubernetes with Zabbix, we will explore the functionality provided by the Kubernetes integration in Zabbix and discuss use cases for monitoring and alerting on events in a cluster.

We will review how Zabbix handles the following:

🔹 Node and Component Discovery: Uncovering control plane components, each node, and the associated kubelet
🔹 Node and Kubernetes Performance Metrics: Indicators and data points about the machines running in the cluster
🔹 State Monitoring: Monitoring and alerting critical status changes within the cluster

🔹🔹 Note: The last video showed a managed EKS cluster. Control plane components cannot be discovered in an EKS cluster because AWS does not make them directly available through the API. To demonstrate the integration's full capabilities, we will use screenshots depicting a cluster created using the kubeadm utility.