I'm not sure if I understand your problem but I think what you really need is to not use groups and use device classes and zProperties instead.
It takes a while to get used to the different way things can be classified but I'm nearly getting there myself I think. e.g. look in device class /Server/Solaris Templates http://myzenoss:8080/zport/dmd/Devices/Server/Solaris/perfConfig You can see templates in there and where they are "inherited" from. You can add a template there (to be used by all devices of this class). You can copy a template (to add to another class of devices on a different inheritance tree). I have device class: /CommProve/Probe zDeviceTemplates contains Device NtpMon ProbeMon (Device is inherited) (NtpMon is the NTP monitor, copied and added there) (ProbeMon is a custom monitor set) we have created) Device class: /Server/Solaris/iubTG zDeviceTemplates contains Device OSProcess NtpMon iubTGMon (Device inherited from top level) (OSProcess and NtpMon inherited from Server or Server/Solaris) (iubTGMon is a custom monitor set we have created) So when we add probe devices we move them into class /CommProve/Probe and NTP and Probe monitors start working. Similar for the solaris servers, the same monitors run on each server, we just use /Server/Solaris for some servers, we use /Server/Solaris/iubTG for servers running one of our services). -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=22018#22018 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
