Votes: 0Posted On: Oct 08, 2017 10:05:43
Nagios is considered by some to be the “industry standard” when it comes to Open Source monitoring. And, it’s somewhat true, because they were the first to actually get it right.
Zabbix, on the other hand, has the main characteristic of a holistic view of monitoring.
It has a web management system that allows central management. It covers performance, not only statuses, which is one of the most significant lacks in Nagios.
In early days, Nagios had a major advantage as it did not use a database to store information. And hence required less resource. But using the same technology today is no good. Since hardware resource is no more an obstacle.
Nagios still uses same old technique and is managed in hundreds of places through text files, scripts, and manual procedures.
Zabbix, on the other hand, uses web-based management interface which is centralized through their database.
Nagios ecosystem is based on hundreds of different patches. In order to make a simple change, it’s necessary to patch a huge architecture code and manually compile. Let’s bear in mind that Nagios’ configuration is based on text files.
Zabbix is a solid project with a complex and modular architecture, that has grown throughout time with a design directed by the team of architects itself.
Monitoring is not so easy with Nagios as one has to deal with hundreds of custom scripts when made another user it almost become some sort of Enigma to decode.
Nagios ends up being a strange mix between software and custom development.
It is no doubt Nagios is the widely known and the oldest monitoring tool in the industry. But it becomes a strenuous to work with Nagios as you need a team to manage and who are capable of understanding the system well enough. The learning curve with Nagios is steep whereas that is not the case with Zabbix.