My starter for 10......

1. Ability to monitor processes and services for device classes (not just a global default and a specific device instance)
2. Automation to move devices from /Discovered to more helpful device classes - see docs/DOC-3540
3. Ability to export graphs and reports - to separate webserver and to pdf files.  Fix the "export all" button.
4. Good documentation on ZenPack design
5. Good documentation on new architecture in Zenoss 4 - event subsystem, Rabbit, Zope database in MySQL,..

Cheers,

Jane

Going on from James' point about scheduling command checks...

1. Scheduling zenmodeler runs - not just frequency. 

Cheers,

Jane

This is excellent feedback!

I will encapsulate a formal response back re: current list of feature requests over the next couple of weeks with roadmap (Core vs. Commercial) alignment included.

Some of the feature requests are in the commercial product today i.e. dependency mapping and intelligent event suppression at the service level, but many of them aren't and are just plain good ideas.

Please keep it coming team ZCA and thank you for taking the initiative.

for event suppression i don't want a complex service suppression but only a simple event suppression to avoid ping down event from remote network if a its remote gateway fail

Much better user interface for creating event transforms.  The tiny window from Event Mapping -> Edit is a joke.

Cheers,

Jane

Not sure if this thread is still valid or if this feature is taken care of in 4.2 (only 4.1.1 for me so far).

1: Run commands against components.

It seems that the commands menu in a device (and in the events window) only seems to run against the device, not the component selected in the sub-window or the component noted in the event.

So if I had a command to start, stop or restart a windows service I would need a command for each service I can predict restarting rather than one command which would take device/component or evt/component as the service I wish to restart.

2: A context-sensitive action (cog-wheel option) for the Infastructure side window that lets me run a remodel against an entire device-class, group, system or location.

3. Ability to link network ranges to a location (I think some preliminary work has already been done in Zenoss for this) and have the regular modeling adjust the location for the device depending on it's IP. Probably need a setting against devices to allow prevention of automated location changing based on IP).

Great if you're monitoring Laptops and devices by host names which might xenmotion/vmotion between sites and pick up new IP addresses.

4. Not so much a feature but it'd be nice to have a lower, alternate licensing price for user devices (e.g. desktops) as opposed to servers.  Likely some definition required around it to specify systems providing for only a single user or a single user at a time (workstations) and not using extended monitoring or something.  Lawyers can figure it out but it could be good for sites with thousands of small registers in stores or terminals in branch offices and other such devices which are often considered far less vital than the full servers but would add some small value if they were all monitored.

AND/OR a license for modeling devices only. i.e. the ability to discover and model devices for asset registration, an up-to-date CMDB and general tracking but no permission to run any monitoring template (even pings) against the device.  Possibly need to restrict frequency of modeling.

So, I might buy 500 Server Monitoring licenses, 1000 User Monitoring licenses (Head office PC's/Laptops) and 6000 Modeling Licenses (store registers/printers) to cover the business needs.  You might even get some customers who wish to use it as a pure CMDB/asset management system and only buy Modeling licenses.