This question ties into my other post from a few moments ago. If for any given device you happen to be collecting and checking on:
- a small handful of specific processes (ie, Processes) - all partitions, cpus, memory, network interfaces, etc - network checking the ports (ie, Services) I'm wondering whether Zenoss does a full snmpwalk each and every time, whether it does something very very specific to what is being sought, or whether it's somewhere in-between, such as doing checks based on the zCollectorPlugins. If the latter, then perhaps I need to pare some of this stuff down. When I first set it up, I basically threw just about every zCollectorPlugin available. There could well be a few I could do without. Here's what I have now: zenoss.snmp.NewDeviceMap zenoss.snmp.DeviceMap zenoss.snmp.InterfaceMap zenoss.snmp.RouteMap zenoss.snmp.IpServiceMap zenoss.snmp.HRFileSystemMap zenoss.snmp.HRSWRunMap zenoss.snmp.CpuMap zenoss.snmp.DellCPUMap zenoss.snmp.DellDeviceMap zenoss.snmp.HPCPUMap zenoss.snmp.HPDeviceMap DellDeviceMap HPDeviceMap DellCPUMap DellPCIMap HPCPUMap So to recap: 1. Is there a way to tell (based on a device which has already been modeled) which of the above are in active use? 2. If one of the above can't be used by the target device, does it generate unnecessary traffic only when modeling the device, or each and every time it polls it? 3. In general, does Zenoss do an efficient job of querying via SNMP, or does it do a lot of repetitive reconnects during a single monitoring pass? I think that's it. If there are any other performance/architecture concerns I should be paying attention to, let me know. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17330#17330 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
