Zabbix vs grafana vs kibana

I am studying grafana for log management and system monitoring. I found that kibana is also used for one process. I just don’t know when to use kibana and when to use grafana and when to use zabbix?

+7
source share
2 answers

Zabbix is a comprehensive monitoring solution, including data collection, data archiving (trends, compaction, ...), a visualizer with dashboards, alerts, and some management support for escalating alerts. (look at collectd , Prometheus , cacti . They are all able to collect data)

Grafana is a data visualizer. He can read data, at least from prometheus , graphite and gum . Its main purpose is to visualize things in user panels and relate things, possibly from different sources. For example, you can see the processor load (for example, ascent data from Prometheus) with good annotations related to some special event in the log file (of course, it is loaded from elastic)

Kibana - visualization + analytics on the registered data in the elastic . Take a quick look at the kibana to find out. This is a must-have tool when you need to look for your logs (various services, various servers) in one place.

+11
source

Zabbix is ​​a monitoring solution that works with active + passive agents that can "measure" things on your systems. Based on these measured values, you can perform actions / alerts, etc. In addition to this, he builds good graphics using a disk / processor, etc.

Kibana / Grafana, on the other hand, receive information from logs sent from your systems. They do not actively monitor, and alerting / messaging is not their main concern. (If at all possible ...?) They do a great job with all your log files.

So, in short: - active / passive monitoring + change = Zabbix - centralized log management = graphane / kibana

This is also not one or the other, they can also be combined

+3
source

Source: https://habr.com/ru/post/1260566/


All Articles