Kubernetes monitoring with Zabbix - Part 2: Understanding the discovered resources
HTML-код
- Опубликовано: 7 мар 2023
- Learn how to monitor your Kubernetes environment with Zabbix!
In this video, we will take a detailed look at the metrics collected by the official Zabbix Kubernetes template.
Part 1 of the video series is available here: • Kubernetes monitoring ...
Download the official Zabbix Kubernetes monitoring templates:
www.zabbix.com/integrations/k...
Download the official Zabbix Helm chart:
git.zabbix.com/projects/ZT/re...
This video overview is provided by The ATS group:
The ATS Group is a Zabbix Certified partner and provides a fully inclusive set of technology services and tools designed to innovate and transform IT. Their systems integration, business resiliency, cloud enablement, infrastructure intelligence, and managed services help businesses of all sizes “get IT done.”
#Zabbix #Monitoring #LinuxMonitoring #kubernetes #containers #docker #containermonitoring #BusinessMonitoring #DataCollection #OpenSource #ProblemDetection #alerting #SoftwareDevelopment #Linux #CentOS #RHEL #Ubuntu #Debian #SecurityMonitoring #Observability #LogMonitoring #cloudmonitoring 
Наука
I have walked through both guidelines but I am not getting the discovered worker-nodes. Is there a step missing?
DO we need 3 different machines to successfully run Zabbix ? 1 for Zabbix component, 1 for database and 1 for Web server ? OR 1 machine would be enough to test it for like 20-30 machines ?? and what is the most stable version of Zabbix to run with Centos ?? and if possible please suggest the cpu, memory , requirements to monitor up to 50 machines ..
Does Zabbix 6.2 requires zabbix server to be installed ?? In the documentation it only says proxy, agent , agent2 and java gateway... does it mean it does not need zabbix server ??
what are the major differences between Zabbix 5 and Zabbix 6 ?
Trying to install zabbix 6.2 , on amazon linux 2 and getting below error :
Error: Package: zabbix6.0-selinux-6.0.14-1.el7.noarch (epel)
Requires: selinux-policy-base >= 3.13.1-268.el7_9.2