jmp242 wrote: > 1. Windows WMI "crap" both works well for us, and is pretty much what has us > using Zenoss. I think it is VERY important to keep the Windows integration. > > Beyond that, I pretty much have to agree, though not necessarily with the > tone. Fix the bugs. We've got quite a bunch of features, but they need to be > more reliable. > > Write up some of the forum info in a Troubleshooting guide. Especially lots > of the "How would *anyone* EVER know this from the docs? I really like Chet > Luther coming here and his advice is gold, but does he like telling every new > user to delete *.zec files, or that the MySQL Zenpack monitors v5 and you > have to twiddle a hidden option for v4? > example: > > > zenmigrate --step=MaintenanceWindowCatalog > zenmigrate --step=TwoTwoIndexing > > Is there any indication in the Admin guide you can apply arguments like this > to zenmigrate? Seems important with upgrading being a little tricky for many, > maybe there ought to be an upgrade guide/troubleshooting guide. In the end, > having this documented in *one* place for end users to look would save you > trouble tickets, forum answer time and make happier users. > -- > James Pulver > Information Technology Area Supervisor > LEPP Computer Group > Cornell University >
I can agree with everything above. Excepting the strange issues I'm having with zenwin and WMI after moving to 2.2.1 (which just displaced my old strange issues with zenwin* and WMI in 2.1.3), the fact that I don't have to install an agent on every single server is a good thing in my book, and is one of the main reasons we are (trying to) use Zenoss in production. I don't necessarily agree with the tone either (but hey, I've had my days like that, too ;-) ) but I wholeheartedly agree that a "maintenance release" would be nice. I think we were told at a RedHat conference about a 8 months ago that the next release (2.1, maybe? Don't remember) was going to be BIG on stability, etc. In many respects I'm still looking for this. New features are really nice and all, but when the existing features don't quite work right and are as buggy as some parts of Zenoss happen to be, sometimes you need to forgo the nifty new features and work towards rock-solid stability--*especially* for a system that is supposed to monitor every other device on the network... -- seth wright ([EMAIL PROTECTED]) windows engineer 540.568.2912 (office) james madison university -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21855#21855 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
