Zabbix_logo_twitter_bigger

Zabbix Review
Nagios vs Zabbix: If you are fed up with Nagios or doing a brand new deployment, take a serious look at Zabbix

 
10049
3

Everyone is familiar with Nagios, which is often considered the de-facto standard for monitoring. The other tools in that general category are OpenNMS, Zenoss, Groundworks, HyperIQ and others. I am only talking here about tools that would qualify in the NMS category: something that really tracks different systems and devices across the entire infrastructure.

A couple of years ago, I was so tired of Nagios that I was ready to try something new. A couple of tools didn’t make the list, simply because of the “fremium” model. The basics are there, but anything more typically carries a hefty price tag.

I decided to try Zabbix and I have pretty much been a fan ever since. One caveat here, is that I am talking about version 1.8.x. Version 2.0 just came out and offers a few notable improvements, which I haven’t tried out yet. A couple of things that look very promising are: Direct JXM support, multi-homed hosts, and mounted filesystem discovery. Full list of changes is here

As an ove...


Disclosure: I am a real user, and this review is based on my own experience and opinions.


3 Comments

Picture-solution1381
untergeekReal User

Nagios is for masochists who are content to live within the ecosystem they first learned, or for people who want a solution cobbled together like Legos in one ugly lump.
While I prefer Zabbix, any number of systems are preferable to Nagios with regards to having a unified system that does much out-of-the-box, rather than a bunch of disparate bolt-ons added after the fact.

02/05/13
Picture-pedro_sousa
Pedro SousaReal User

Over the years I've been using Nagios, Zenoss, GroundWork, Cacti and other SNMP+MRTG solutions; since I've found Zabbix, it's been my number one choice. However, it still has some issues with the Reporting capabilities that need major improvement. From a "techs" point of view, Zabbix provides reliable metrics and a fairly simple implementation (with some tweaks discussed on this article) but from a managements point of view, it lacks the "beautiful graphs and reports" that Management "likes"!!! I'm not very happy with the time I'm asked to produce reports on my systems and have to setup the same reporting parameters time and time again...

02/13/13
George-wenzel-li?1376406550
George WenzelReal User

The old-school systems produced graphs every time data was gathered. This resulted in a fast user experience displaying graphs, but it caused the number of values per second to be limited by the number of graphs per second you can produce.

Zabbix dynamically creates the graphs on demand. This reduces the number of times it much produce a graph, pushing up the number of values per second you can capture. But as the reviewer noted above, screens and individual graphs can display slowly if they contain too many data points.

I agree with the reviewer that many or most of the default poll rates in the templates have excessive poll frequency. In fact, they are so high as to have an impact on the machine your are polling if you have very many values you are pulling. Sometimes I think that the people that create the templates only have one machine they are monitoring, and they set the poll frequency high just to have quicker graphs appear when setting up a new zabbix server. Nothing is more boring than spending a couple hours setting up a monitoring system, only to have a bunch of graphs with single dots on them because your polling cycle for disk space is every 15 minutes. But regardless of the reason for it, I think it is irresponsible to release templates with inappropriate polling cycles.

But back to the graphs, if you have too much data, an otherwise simple graph will take a long time to display. On a screen this gets worse because you are displaying multiple graphs. So to get the best screen display performance, reduce the polling frequency to the lowest value that still produces good graphs.

I have been knows to produce two objects for the same item, with different polling cycles. A long polling cycle for graphs that appear on screens and public viewable pages, and faster polling cycles for detailed data collection to be used in debugging.

I've used nearly all of the network monitoring systems in the 30+ years I have been monitoring networks. Zabbix is my favorite for most applications. I do use more advanced commercial systems such as NetMRI, as the commercial systems can do things like discover all of your systems, and self configure. Commercial systems like NetMRI also do deep inspection, such as VOIP quality analysis, that Zabbix simply isn't designed to do.

I can do anything with Zabbix, anything that I have time to configure. But to be fair, systems like NetMRI can be configured for very large environments in 5 or 10 minutes, out of the box. But when I want to do something special, that I create code for myself, I don't use systems like NetMRI, I use Zabbix. Zabbix is my favorite general purpose network monitoring system. And to be fair, Zabbix is a commercial system too, when you need it to be.

Tools like NetMRI have a lot more power to self-configure, but that power is not free... The NetMRI quote for the hospital I worked for was $300,000!! The commercial version of Zabbix was much lower. And with some careful work with discovery templates, you could still get some self-configuration out of Zabbix.

Solar Winds is another commercial tool in the same space as NetMRI. Solar Winds is nice, but the performance is impacted by the fact it runs on Windows, so it takes more hardware to monitor large enterprises, but it is comfortable for the Windows geeks. I'm not a Windows geek...;)

George

02/14/13