Hi All,
First, im not the biggest zabbix guru in the world, for the most part the way I use it is via its API from another application.
The goal im trying to achieve is to figure out the overall status of the things being monitored by zabbix by querying the API. For about the last year the app itself just gets every host, then gets every trigger for each of those hosts and polls that fairly frequently. It works ok, but never took into account things like maintenance or acknowledgement. Maintenance isnt too hard to add because its on the host object. But as the number of things being monitored in zabbix increases, polling has become quite lengthy. The ultimate goal is to really reduce the entire zabbix status to a single green/yellow/red box.
Im about to re-write the app from scratch and im wondering what insight anyone might give me about what is the most efficient way of achieving that goal?
My initial thoughts were to get all the hosts, then get all the new events (since the previous poll) created by triggers and then check that trigger for its current state. It also gives me the ability be able to ack the event from the app itself and have zabbix know that is the case (currently this is done in the app by just ack'ing it and the app remembering between polling intervals that an active trigger was already acknowledged but never goes back to zabbix acknowledgements). The alerts api is also possibly useful here.
First, im not the biggest zabbix guru in the world, for the most part the way I use it is via its API from another application.
The goal im trying to achieve is to figure out the overall status of the things being monitored by zabbix by querying the API. For about the last year the app itself just gets every host, then gets every trigger for each of those hosts and polls that fairly frequently. It works ok, but never took into account things like maintenance or acknowledgement. Maintenance isnt too hard to add because its on the host object. But as the number of things being monitored in zabbix increases, polling has become quite lengthy. The ultimate goal is to really reduce the entire zabbix status to a single green/yellow/red box.
Im about to re-write the app from scratch and im wondering what insight anyone might give me about what is the most efficient way of achieving that goal?
My initial thoughts were to get all the hosts, then get all the new events (since the previous poll) created by triggers and then check that trigger for its current state. It also gives me the ability be able to ack the event from the app itself and have zabbix know that is the case (currently this is done in the app by just ack'ing it and the app remembering between polling intervals that an active trigger was already acknowledged but never goes back to zabbix acknowledgements). The alerts api is also possibly useful here.