Slashdot Mirror
Best OSS Systems Mgmt App You Never Heard Of
FLOSSisnot4Teeth writes "You probably are familiar with Nagios and Webmin as two of the most widely deployed open source systems management applications. However, this month's SourceForge.net Project of the Month is probably a newcomer to open source systems and network administrators. Zenoss Core is a systems monitoring platform, released under GPL and over the last year it's become one of the most popular SF.net projects. Unlike most of these new "commercially backed" open source projects, Zenoss Core is the only version, their corporate sponsor doesn't offer a "pro version". Also their developers have been committing code back to other projects like RRDTool and Twisted. I have been playing around with Zenoss for about six months and have been totally impressed. Would be curious to see what other Slashdot readers think." SourceForge.net and Slashdot are both owned by OSTG.
This seems a bit reminiscent of AdventNet's OpManager system. I would like to point out right now, though, that OpManager is about 700$ for a decent license that even compares to the kind of coverage you get from Zenoss. I wouldn't compare this app to Webmin so much; webmin controls only local system programs and some minimal enterprise software. This dives into the devices end of things as well, providing a decent number of MIBs. I'm very impressed by how the management console includes inventory on devices. Documentation seems decent, but then again I've been working with enterprise networking and systems management for several years. Even at that, this tool isn't demeaning to those who have prior experience. All and all a great OSS project and I look forward to seeing it continue to improve with time.
Take a look at http://www.zenoss.com/. They just didn't link it in on the Source Forge site.
Zenoss
Jan 26, 2007
I may have finally found the perfect monitor solution for my network: Zenoss. I have been using Nagios + Cacti + Smokeping for quite a while now. It works, but it's not integrated, and for many services, I'm running 2-3 checks. Running those every 5-10 minutes generates a tremendous amount of traffic (during the last 2 weeks, the monitor station has caused 20% of all traffic crossing the primary firewall!). The closest all-in-one I'd found previously was OpenNMS, which is so difficult to really understand and manage well, and so didn't fit my needs. I'd given some thought to rolling my own in Ruby, but just don't have the time for such an undertaking.
So while browsing the rPath/rBuilder site this morning, I discovered Zenoss. It's Zope-based, which I find a bit interesting. But from what I've seen in the 30 minutes I've had it running, the developers are right on with what I've been looking for. It has auto-discovery support, placing everything into a "/Discovered" group if it can't pick the right group on its own (the firewall was placed into the "/Network/Routers" group since it was part of the discovery chain). But it is smart enough to correlate different IPs to a single device, which OpenNMS can't do. It also supports Nagios plugins (though only via ssh and not nrpe), so I can leverage that investment while I evaluate the Zenoss way of checking.
There's also a built-in syslog catcher, so it can correlate log events to devices, which could be another huge time saver. And it has asset/inventory management so I don't need to keep that data separately either. What can't this puppy do?!
You can install from source or RPM, and there's a vmware image available too. It requires Python 2.3.5+ and MySQL 5.0.22+. Since I wanted to run on my Debian Sarge monitor station (which already has access to all the devices to manage), I had to upgrade the DB. Easy enough with the backports. The only trick I ran into there is that the install process requires port 8100 be available. You can change after install, but I couldn't find a way to change prior. The installer doesn't notice if the port is already in use, it just silently fails, and so when starting the Zope DB setup, it gets in a loop of printing "." (dots). Finally realized I had to shut down a Mongrel-run Rails app to get it going, and it worked perfectly. (Bug #933 has been filed.)
Stay tuned for more, as I will be playing with this ALOT over the next few weeks!
Besides the python script to create a WMI monitor, zenoss does have good SNMP support - when you run the Informant http://www.wtcs.org/informant/ SNMP extensions.
Slashdot is for anything the Slashdot staff feel like approving.
It's not for satisfying anonymous cowards.
Advanced users are users too!
Interesting how the submitter writes the post suggesting as if they're a user....
"I've been playing around with it for six months and have been totally impressed!"
Easy to be impressed by your own products, isn't it?
I am as big a PostgreSQL bigot as you are likely to find, but I don't see the problem with using MySQL for storing monitoring data. I mean seriously, why should I care if the application stores the fact that my servers still respond to pings in a transaction safe manner? Nagios, which I currently use, stores this information in flat text files.
I'm using Nagios on a group of core network devices. I have to be super careful not to perform an "up2date" on it (using RH 4.0 EL) because the Nagios packages always overwrite my config files. But Nagios is good, and it's been very useful. It took me a few days of work to get it set up the way I wanted, and it's been a charm ever since.
A few weeks ago someone posted an article on the top ten OSS projects to watch, and Zenoss was one of those projects. I downloaded it to experiment. I had it up and running in about 20 minutes, on Ubuntu. It's far more powerful at its ability to gather data from nodes. And setup is far less manual. Network discovery worked very well. It found devices on our network that we didn't know were out there. It required no integration with other packages. The interface is also more intuitive in some areas, such as viewing event histories. But, it's more challenging to find performance charts the first few times.
I especially liked the automatic snmp walk through the MIBS on each device. This makes it much easier to pull statistics from it, without having to edit text files. The MRTG-style charts are also good. I wish they were more readily configurable. I also wish there were more MIBS in the distribution, but you can find most by carefully searching equipment provider's web sites.
All in all, After running it side by side with my Nagios setup for a couple of weeks, I like it much better. And I'm moving more SNMP agents into my network just because of Zenoss.