Here are some of my needs: 1) Better, more in-depth documentation.
2) Ability to create device templates in terms of defining Processes and Services to monitor. This would also lock them these metrics by default. This way, I can say: "Add device X to /server/linux/webserver", and it would automatically monitor and lock all OSProcesses and IPServices that goes along with that device class. 3) Fix issues with OSProcesses showing duplicates. I posted about this here: http://community.zenoss.com/forums/viewtopic.php?t=6049 I am having issues with duplicate Processes showing up when I already have the same processes monitored and locked. This is quite annoying and causes many false alarms. The only (temporary) fix is to remove both of the duplicates, then remodel the device, then re-lock the process. I've had similar issues with IPServices as well. 4) When renaming a device, you lose all of your RRDs for that device. This should be taken care of by identifying devices (in the backend) by an ID, and not so much by hostname, which is prone to change. ...more to follow! -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=21500#21500 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
