There is no enterprise version of the ZenJMX plugin. And yes I guess you are correct in that aspect. But I guess I expect some level of quality even in the open source version.
At least some notification of the status or "stage" if you will of plugins and features of zenoss would be beneficial. Or at least make it clear what is currently being "tested". What needs to be tested. etc. There is no current indication (other than all the complaints I read and the bug tracker) about the current state of zenoss and what needs to be done. Why would I recommend the Enterprise version of Zenoss when the official core releases still contain many bugs? Maybe the zenoss team should have more strict guidelines as so what it considered an official stable release because I do believe that the quality core open source version reflects the quality of the enterprise version because there is nothing to indicate otherwise. jmp242 wrote: > Have you evaulated the Enterprise version? Because all you post sounds > like you want/expect commercial support + highly tested releases. Zenoss > Core is the testing ground for things before they go in Enterprise (as I > understand it). It's like Fedora Core vs RHEL. > -- > James Pulver > Information Technology Area Supervisor > LEPP Computer Group > Cornell University > > > > peterd wrote: > > > I'm a relatively new zenoss user and have decided to not recommend zenoss > > to my organization. Why? > > > > Not because zenoss is bad. Not because I don't see potential. But because > > it just isn't worth it to sort through all the problems to get a viable > > monitoring system. > > > > Also, the zenoss team tends to release plugins and patches that have had > > absolutely no testing. The ZenJMX plugin is an example of this. If you > > release something as buggy as this why not mark it as an alpha or beta > > plugin? Why not state that it has not be tested or used in a production > > environment? Why advertise it as a functional addition to zenoss? I've > > wasted hours trying to find out why certain things weren't working when all > > I needed was to know nothing has been tested. > > > > Then there are all the what ifs. What if I work out tons of the bugs and > > finally get a nice production system ready to monitor and the hard drive > > dies before I can get a chance to do a backup? There goes hours of not days > > of work lost because I decided to use zenoss in it's current condition. > > > > I think the devs/management should be more open about the current state of > > zenoss and its plugins instead of using potential users who try zenoss as > > the QA team. And if there is an open problem or question on the forums at > > least respond with "We don't know" or "We acknowledge this problem". But > > again and again I see unanswered questions. > > > > Ok rant over. > > > > > > > > > > > > > > > > _______________________________________________ > > zenoss-users mailing list > > [email protected] > > http://lists.zenoss.org/mailman/listinfo/zenoss-users > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=18241#18241 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
