Eight important comparative conclusions between ZABBIX and Nagios decisions based on business environment requirements

1. 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 is easier to getstarted with, but the Zabbix interface is more aesthetically pleasing and more difficult to get started with.

2, drawing display:

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: the Zabbix of drawing function

3, the 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 feel a lot more cool

4, Custom monitoring services:

Both Zabbix and nagios are self-writing plugins, and then modify the client-side configuration file.

Conclusion: The two are the same degree of ease

5, Batch monitoring host:

Nagios for bulk monitoring hosts, a script is required to add host to the server side and copy service files.

Zabbix the server side of the automatic registration rules, after the configuration of rules, the subsequent new client side does not need to operate on the server side.

Conclusion:The subsequent batch monitoring implementation of Zabbix is simpler

6, 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 clicks canbe, Zabbix use to be more cool.

7, 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

8. 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.

Summarize:

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 theproblem 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, allin 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.

Eight important comparative conclusions between ZABBIX and Nagios decisions based on business environment requirements