We detect problems before the customer does and before it actually happens using the predictive functions in Zabbix. Zabbix gives us a single point of truth.
The most valuable features are the low-level discovery, auto registration, host discovery, integration with other tools, and the zbxdb plugin for database monitoring
Very good templates
I would like to see a more flexible mobile client, and better HA out of the box.
It would also be very interesting to have a GUI on the proxy server[s]
I have been using this solution for eight years.
Stability of the product (servers and agents) was one of the key factors we checked. The agents normally have a low footprint and are very resource friendly.
Especially when using postgres with the timescaleDB option, the performance improved a lot because data deletion is now done by dropping partitions, which saves lot's of database time. We are confident that zabbix kan keep working for us while we grow. In the end, the bottle neck will be the database but we see a lot of options to stretch this.
Zabbix support works through various channels and works responsive. We are also very glad with the community support where we also share our experiences. Currently there is an active community in Telegram https://t.me/ZabbixTech
Earlier we used all kinds of other tools, all for a part of the stack. Oracle enterprise manager for oracle databases, PEM for postgres databases, SCOM for Windows, prtg for network, appman for applications. This required to run and maintain all those tools .... Now consolidating to 1 saves a lot of time and gives a single point of truth.
The initial setup is easy. Making it completely HA required some work but if you are familiar with the redhat tools it is not hard.
We implemented the zabbix solution our selves. A team consisting of a Linux admin and a postgres dba that both know Linux and zabbix setup the infra structure. The other teams gave input for their metrics, thresholds and views.
Combined with the other tools that we phased out the ROI will be within 1 year. One of the things we save a lot of money on is the replacement of SMS by an other notification service.
Make a POC, start simple and let it grow. The servers are created with good performance by design. Memory for the caching, both on the database as on the zabbix server are important. As database backend choose postgres with timescaleDB. This save many hours housekeeping processing. For proxies, sqlite will do nicely. Involve a dba for the database setup.
We checked the above mentioned options. Zabbix came out as a winner. Simple, good web application, no need for fat clients which makes maintenance simpler. Zabbix does not have the nicest GUI, compared with some above but it is certainly acceptable, especially when pricing is taking into account. Especially with the postgres database in combination with the timescaleDB options is has an excellent performance. It has a clean database design and handling.
If state of the art reporting is important, integrate with grafana. It can be done via the api and directly on the zabbix database.
If performance and scalability is important, use postgres with timescaleDB as database backend. This wins hands down compared to mysql.