Evaluated these versions. Core: 2.0.x -> 2.2.0
Enterprise 30day with support: 2.1.2 They all had their fair share of issues/bugs/crashes/dbcorruption/lack of docs, yet I learned quite a bit :) I will mention Zenoss Support was pleasant with some nice folks handling questions and we got a nice graphing walkthrough by Chet Luther which was helpful back when we first tried figuring out the template system. I still have great things to say about the company and their ideas. They are great helpful people I just wish the software was a bit more mature. I would for SURE check out future releases in about 3-9 months. Who knows once things mature more perhaps I'll have another go. The foundation is there we just need stability and docs. As for replacement we dont know that one yet. Zenoss really felt like the right answer for our needs. We're thinking OpenView NMS component or something like Cacti/Smokeping even though I wish they were more integrated. We're kinda in the dark about our next solution since there really isnt a great free NMS tool out there. They all do something great but fail miserably at some other required functionality. Zenoss was the closest to integration that we could find. >From my experience I'd say you have 4 things, pick 3. It pretty much works out. Cheap, High Performance, Extensible, Stable Hopefully I've filled in some gaps in my reasoning. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21191#21191 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
