HI,
We have followed instruction How to setup service monitoring https://www.zabbix.com/documentation...rvices/example
On example there is Cluster with two nodes, and it change status to another in case both nodes have issues. We want to do bit other way around.
So lets say we have Cluster with two nodes. If one node get down it would change Zabbix service root status on tree to any status except OK, but would not impact SLA calculation.
In general if we have SLA for a cluster, one node should not impact SLA as other node still take care of availability. But on Zabbix services we want to see that there some issues.
Any idea if any zabbix services statuses could act similar as OK for SLA calculation (do not count downtime). We tried to set to Information, but it still counts downtime.
Currently we are on Zabbix 6.0.x, but also if there are solution on newer version would be good to know.
We have followed instruction How to setup service monitoring https://www.zabbix.com/documentation...rvices/example
On example there is Cluster with two nodes, and it change status to another in case both nodes have issues. We want to do bit other way around.
So lets say we have Cluster with two nodes. If one node get down it would change Zabbix service root status on tree to any status except OK, but would not impact SLA calculation.
In general if we have SLA for a cluster, one node should not impact SLA as other node still take care of availability. But on Zabbix services we want to see that there some issues.
Any idea if any zabbix services statuses could act similar as OK for SLA calculation (do not count downtime). We tried to set to Information, but it still counts downtime.
Currently we are on Zabbix 6.0.x, but also if there are solution on newer version would be good to know.