Nagios vs. Zabbix

Nagios vs . Zabbix

Web Features:

Nagios Simple and intuitive, alarm and data are on the same page,* * *, Red is the problem. Nagios Web side do not make any configuration.

Zabbix monitoring data is separate from the alarm, viewing the problem item needs to look at the trigger and view the data in the latest data view. and Zabbix has many other configuration items

Conclusion: For beginners, Nagios Easier to get started, but Zabbix the interface is more beautiful and more difficult because of the ability to get started.

Drawing Show:

Nagios requires additional plug-ins, and the plugin does not paint beautifully.

Zabbix carry the drawing function, and can manually put a number of monitoring items in a diagram to show, but also to select the graphics category, there are : line, area, pie, column chart, etc. to choose from.

Conclusion: Drawing function Zabbix with the cool

Default monitoring:

Nagios comes with few monitoring items. Manual configuration is required for monitoring changes such as multiple partitions and multiple network cards.

Zabbix comes with a lot of monitoring content, feel Zabbix at the beginning for you to do a lot of things, especially for multiple partitions, multiple network cards and other automatic detection and monitoring, that moment is very pleasantly surprised, very worry feeling.

Conclusion: Zabbix It feels so much better.

Custom Monitoring services:

Zabbix and Nagios are self-writing . and then modify the client -side configuration file.

Conclusion: The two are the same degree of ease

Batch monitoring host:

Nagios for the bulk monitoring host, you need to script the server side to add host, and copy the service file.

Zabbix the automatic registration rules are configured on the server side, after the rules are configured, the new client side does not need the server The end of the operation.

Conclusion: Zabbix easy implementation of subsequent batch monitoring

post-Batch modification monitoring services:

Nagios modifies all of the host's services files with a script , adding new services.

Zabbix only need to manually add a monitoring item to the template.

conclusion: a need to conceive the implementation of the script, a few mouse points can be, Zabbix use it to be a little more cool.

Alarm Implementation:

Nagios alarm using plug-ins, as long as the plug-in can do the alarm,nagios can be achieved, regardless of mobile mailbox and other.

Zabbix with Nagios

Conclusion: The two are consistent

Other Extensions

Zabbix comes with web monitoring, comes with process and port monitoring, and of course there are some other features I haven't explored yet.

Nagios also has plugins that don't have to write their own plugins.

Zabbix provides API interface to facilitate other platform calls. However, Nagios can be configured directly by the program management.

Conclusion: A time spent in groping, a time spent on writing scripts, not to say who good, almost.

Summary:

Nagios spends a lot of time writing plugins, andZabbix spends a lot of time exploring features.

Nagios is easier to get started,andNagios will be there for two days,Zabbix two weeks.

Zabbix Drawing features more powerful than Nagios

Zabbix for batch monitoring and service changes, the operation is more concise;Nagios It's easy to write an automated script, and the problem is that writing an automated script is a hassle.

for enterprise monitoring applications, both can achieve large-scale monitoring, are sufficient to meet user needs, there is no absolute good or bad. Zabbix is a business software open source, all in one way experience good,Nagios is freeware, many plug-in combinations.

The two are like Windows and Linux , one that has all done well and one that can be customized for all.

Nagios vs. Zabbix