The current distributed setup is primary meant for offloading. In very large environments with dozens of colocations around the globe you're going to get a large amount of wrong failures just because of network outages.
I would like to see a way to have parallel monitoring and trigger dependencies so an event becomes true only, if a configurable number of zabbix instances are triggering the event.
i.e.
Needed events for Server A in Colocation Y: 4
Zabbix A: Reports failure of Server A in Colocation Y
Zabbix B: Reports failure of Server A in Colocation Y
Zabbix C: Reports failure of Server A in Colocation Y
Zabbix D-Z: Doesn't report failure of Server A in Colocation Y
In this case no event for Server A in Colocation would be triggered.
Moreover, it would be great to have a Trigger type for this scenario so the ops team get notified about a possible network outage on the Zabbix A-C instances.
If there's already a way to do this, I just havn't seen it yet and it would be great to point me into the right direction
I would like to see a way to have parallel monitoring and trigger dependencies so an event becomes true only, if a configurable number of zabbix instances are triggering the event.
i.e.
Needed events for Server A in Colocation Y: 4
Zabbix A: Reports failure of Server A in Colocation Y
Zabbix B: Reports failure of Server A in Colocation Y
Zabbix C: Reports failure of Server A in Colocation Y
Zabbix D-Z: Doesn't report failure of Server A in Colocation Y
In this case no event for Server A in Colocation would be triggered.
Moreover, it would be great to have a Trigger type for this scenario so the ops team get notified about a possible network outage on the Zabbix A-C instances.
If there's already a way to do this, I just havn't seen it yet and it would be great to point me into the right direction
Comment