i thought i could share here some of the experiences with the tools we've been experimenting with in the last few weeks.
due to some limitations in the zabbix architecture (slow API, "latest data" screen being extremely slow, busy housekeeper, backend DB performance, need for DB partitioning, lack of proper reports etc), we have decided to try some alternatives.
so what we are doing:
pushing some linux server logs (messages, apache, app logs etc) via filebeat to ELK. therefore it makes sense for us to use ELK for zabbix metrics as well. other option we have considered was influxdb, but since ELK is already there, we simply used it and it works fine so far.
there is a very nice node.js application, which reads zabbix data directly from the DB and can push it to elasticsearch - https://github.com/jojohappy/zabbix-relay
we have a simple cronjob, which runs every 5 minutes and loads the last 5 minutes into elasticsearch (i wish there was some native real-time integration in zabbix
)
as a frontend, grafana seems to be the best option, especially when you have this nice plugin - https://github.com/alexanderzobnin/grafana-zabbix
it is using zabbix API and therefore speed is not very good, but you can display for example zabbix dashboard together it any other grafana items (graphs, tables etc).
kibana is nice for analysing logs, but for dashboards, i think that grafana clearly wins here.
i believe that modular setup like this is the future (as opposed to current "monolithic" zabbix architecture) and i hope next zabbix releases will try to integrate as much as possible with at least some of those products.
we are still in the early evaluation phase, for example still missing some reports, but hopefully we will find a way here also
we will also definitely consider the logstash zabbix output - https://www.elastic.co/guide/en/logs...ts-zabbix.html
anyone else maybe going the same direction?
due to some limitations in the zabbix architecture (slow API, "latest data" screen being extremely slow, busy housekeeper, backend DB performance, need for DB partitioning, lack of proper reports etc), we have decided to try some alternatives.
so what we are doing:
pushing some linux server logs (messages, apache, app logs etc) via filebeat to ELK. therefore it makes sense for us to use ELK for zabbix metrics as well. other option we have considered was influxdb, but since ELK is already there, we simply used it and it works fine so far.
there is a very nice node.js application, which reads zabbix data directly from the DB and can push it to elasticsearch - https://github.com/jojohappy/zabbix-relay
we have a simple cronjob, which runs every 5 minutes and loads the last 5 minutes into elasticsearch (i wish there was some native real-time integration in zabbix
)as a frontend, grafana seems to be the best option, especially when you have this nice plugin - https://github.com/alexanderzobnin/grafana-zabbix
it is using zabbix API and therefore speed is not very good, but you can display for example zabbix dashboard together it any other grafana items (graphs, tables etc).
kibana is nice for analysing logs, but for dashboards, i think that grafana clearly wins here.
i believe that modular setup like this is the future (as opposed to current "monolithic" zabbix architecture) and i hope next zabbix releases will try to integrate as much as possible with at least some of those products.
we are still in the early evaluation phase, for example still missing some reports, but hopefully we will find a way here also
we will also definitely consider the logstash zabbix output - https://www.elastic.co/guide/en/logs...ts-zabbix.html
anyone else maybe going the same direction?
Comment