I am integrating OpenShift Alertmanager with zabbix to monitor alerts like KubeJobFailed, KubePodNotReady, etc., across multiple clusters.
I'm planning to use a single zabbix trapper item to receive all alerts and then configure triggers based on alert severity(e.g., warning, critical)
1. Is this approach feasible and efficient for handling alerts from multiple clusters?
2. How does zabbix manage duplicate alerts periodically sent by Alertmanager, and what's the best practice to avoid clutter while ensuring alerts are actionable?
3. Can I create dynamic triggers in Zabbix based on specific Alertmanager alert labels(e.g., namespace, pod, application)?
Any advice or insights from similar setups would be appreciated.
I'm planning to use a single zabbix trapper item to receive all alerts and then configure triggers based on alert severity(e.g., warning, critical)
1. Is this approach feasible and efficient for handling alerts from multiple clusters?
2. How does zabbix manage duplicate alerts periodically sent by Alertmanager, and what's the best practice to avoid clutter while ensuring alerts are actionable?
3. Can I create dynamic triggers in Zabbix based on specific Alertmanager alert labels(e.g., namespace, pod, application)?
Any advice or insights from similar setups would be appreciated.