Zenoss ZenTech Community

Does anyone know how to increase the amount of work I can give to zencommand in Zenoss 5
With Zenoss 3.2.1, I have 11 production zenoss hosts, and I normally use a combination of extra logical collectors and extra remote collectors.
We have a lot of hosts and a lot of command checks to be done - usually just various versions of curl scripts.

I've been told that Zenoss 5 Core doesn't offer multiple collectors. And I've found adding extra instances of zencommand doesn't work, (it just duplicates the work instead of sharing it..)

I've managed to hit saturation in my test Zenoss 5 host at the same choke point I reached in my Zenoss 3 host, despite the Zenoss 5 test hosts being huge. It's all about saturation on the zencommand daemon..

Subject:	Can someone please confirm
Author:	[Not Specified]
Posted:	2015-10-14 04:55

Can someone please confirm/add to this Without the ability to scale up zencommand/add collectors, my company cannot use Zenoss 5. I'd be really grateful for any help/confirmation of the situation.

Subject:	remote collectors in Core has
Author:	Andrew Kirch
Posted:	2015-10-14 11:32

remote collectors in Core has always been a community supported feature. It would be helpful if someone took over the remote collectors zenpack and upgraded it to work with 5.x.
As of now there is no way to go beyond 1 collector in 5.x.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

Subject:	An interesting proposal
Author:	[Not Specified]
Posted:	2015-10-15 17:55

In fact, I'd be quite interested in fixing a number of useful/essential ZenPacks that enable the Core edition to actually do useful things. I'd also be interested in learning more about why and how things were changed to break these essential additions which were given to you free of charge by coders that helped make your product into something that was good enough for production use.

However, I have been unable to find any explanation of the changes that were made that have the potential to break existing ZenPacks. I have, of course, read the Release Notes and Upgrade Guide, which very briefly mentioned some of the changes that were made, but offered no pointers as to how to adapt ZenPacks to the new infrastructure.

I have also read the ZenPack Troubleshooting guide: http://wiki.zenoss.org/ZenPack_Development_Guide/Troubleshooting

However, apart from addressing one specific problem and instructing people briefly on how to use the python debugger, it doesn't seem to offer any actual information on troubleshooting ZenPacks.

I see there are also resources in the ZenPack Development Guide: http://wiki.zenoss.org/ZenPack_Development_Guide

However, since these are from 2013 and you have changed the infrastructure so drastically, I have my doubts as to whether they are even relevant anymore.

While I'm obviously rather bitter about you breaking the functionality of your product and stepping on the people that have made contributions to improve it while offering no solid information on how they could potentially fix things (which you would likely break again in a future release, rendering their efforts futile) I am actually, for some bizarre reason, considered doing said work.

Is there anywhere you might be able to point us to some resources that would allow us to fix the broken ZenPacks and make them compatible with the new version

Subject:	We're working on making those
Author:	Andrew Kirch
Posted:	2015-10-21 13:31

We're working on making those resources available. You've also created a problem for me. Your username is simply inappropriate. I'm fine with you participating, and frankly, I agree with the points you made, but I need you to recreate your account.
If you have questions, please e-mail community@zenoss.com

Subject:	Zenoss 5 Scaling Zencommand
Author:	[Not Specified]
Posted:	2015-10-12 11:53

Zenoss 5 Scaling Zencommand