List of Modeller Plugins and what they do?

[briffle]

Is there a listing of all the modeller plugins, and what they retrieve?  (for zenoss 3.1) Something similar to advanced->Monitoring Templates?
 
I am trying to whittle down the monitoring to the bare minimum needed for my needs.  So far, for remote systems, I have reduced the SNMP Modelling from 60 seconds (very slow link) to about 6 seconds.  I have also drastically reduced CPU usage on those remote systems from net-snmp.
 
However, I have found this page: http://community.zenoss.org/docs/DOC-9392
but that is about it.
 
I would love to find out the difference between say: zenoss.snmp.DeviceMap and zenoss.snmp.NewDeviceMap.  Not to mention, I have a TON of other SNMP modelling plugins listed, and have no idea what's redundant or unessesary. (IE, how is the Zenoss.Community.DellCPUMap different then Zenoss.snmp.cpumap)
 
 
Is there anywhere I could look?

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/58632#58632





--end--

[themactech]

I think your best bet is to look at the filesystem.
 
Go to /usr/local/zenoss/zenoss/Products/DataCollectors/plugins/zenoss
 
If you open each python modeler, the values it collects should be fairly obvious.
 
Manuel

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/58634#58634





--end--

[johnnynoc]

h5. Here's something I put together for myself:
 
*community.snmp.APCDeviceMap* - Gather information from APC UPS devices.
*community.snmp.CiscoHSRP* - Model Cisco Hot Standby Routing Protocol (HSRP) capable devices.
*community.snmp.CiscoMap* - Models Cisco device attributes.
*community.snmp.CpuMap* - CpuMap maps SNMP cpu information onto CPUs.
*community.snmp.DeviceMap* - DeviceMap maps the interface and ip tables to interface objects.
*community.snmp.HRFileSystemMap* - HRFileSystemMap maps the filesystems to filesystem objects.  (Uses the HOST-RESOURCES-MIB OIDs)
*community.snmp.HRSWInstalledMap* - HRSWInstalledMap finds various software packages installed on a device.  (Uses the HOST-RESOURCES-MIB OIDs)
*community.snmp.HRSWRunMap* - HRSWRunMap maps the processes running on the system to OSProcess objects.  (Uses the HOST-RESOURCES-MIB OIDs)
*community.snmp.InformantHardDiskMap* - Map SNMP Informat sub-agent to HardDisk.
*community.snmp.InterfaceAliasMap* - Extends the standard InterfaceMap to use the ifAlias as the interface's name instead of the ifDescr. This can be useful when many interfaces on the same device have
the same ifDescr.
*community.snmp.IpServiceMap* - IpServiceMap maps the TCP/IP services running on a machine to IP Service objects.  Note that only TCP services can be monitored.
*community.snmp.IpV6ServiceMap* - IpV6ServiceMap creates IpV4 Services from IPV6 descriptions that allow all incomming requests (address ::).
*community.snmp.NewDeviceMap* - Try to determine OS and hardware manufacturer information based on the snmpDscr OID.
*community.snmp.NewRouteMap* - NewRouteMap maps RFC2096 values to interface objects.
*community.snmp.PhysicalEntityMap* - Use ENTITY-MIB to determine physical entities as expansion cards.
*community.snmp.PowerwareDeviceMap* - Map OIDs from Dell Open Manage MIB to get hw and os products.
*community.snmp.RouteMap* - RouteMap gathers and stores routing information.
*community.snmp.SysedgeDiskMap* - Empire SysEDGE disk information.
*community.snmp.SysedgeMap* - Gather Empire SysEDGE disk OS and licensing information.
*community.snmp.UCDHardDiskMap* - Map UCD-DISKIO-MIB OIDs to the HardDisk relation.
 
I found this info in the directory themactech describes below.  Also, if you're using ZenPacks such as DellMon or HPMon you can typically find the same info from the plugins directory of the ZenPack.

--------------------------------------------------------------

To post a reply to the thread message, either reply to this email (recommended) or visit the message page: http://community.zenoss.org/message/58627#58627





--end--