Wednesday, October 24, 2012

EMU Monitoring with Zenoss

That probably should actually read "attempted EMU monitoring with zenoss."

I'm using Zenoss 4. It's really, horribly painful to use. What documentation I can find is for previous versions, and they don't seem to apply to v4. 

There's an easy to use script that actually installs Zenoss. It seems to Just Work, though it assumes that you don't currently have MySQL installed or running, and if you do, you have to remove it. Not a problem on a separate VM or host, but if you're trying to share with another application that uses MySQL, you'll have to install it by hand.

After a bit of flailing, I finally figured out how to add a new monitoring template, so that I could pull in the AP9340s and NetBotz devices (go to Advanced -> Monitoring Templates, had to add a new template to the / path using the + sign at the bottom left).

You then have to select each individual data point and add it to a graph. The names seem to be consistent across devices, so when I tried to change the name of a sensor on one device to reflect it's location, it switched on all of them. There may be a way to work around this, but hell if I can figure it out.

I have yet to successfully load a MIB or ZenPack. The PowerNet MIB that I've been using with my script apparently has some sort of syntax error that Zenoss refuses to load. The handy ZenPacks that Zenoss has to pull this stuff in automatically don't seem to load under Zenoss 4.

Still going to play with it a bit, but I think we might need to look elsewhere for something useful. Aside from the graphing that I've been successful in doing with the NetBotz and 9340s, I've had better luck with bash. Zenoss LOOKS really promising, and has a lot of features that might be handy, but Nagios seems much easier to configure and use for alerting, and I can't get the stuff that Zenoss does that Nagios doesn't do to work at all.

Guess we'll see.