Personal tools
Skip to content. | Skip to navigation
Adds modeler plugin and monitoring datasource to retrieve list of Docker containers and monitor their statuses. Docker Containers modeled in Zenoss device
The VMWare ESX Server ZenPack for Core allows you to monitor ESX hosts and guests via VMWares EsxTop utility. The ZenPack uses the resxtop command to gather performance information about VMware Infrastructure ESX servers.
HPMonitor provides custom modeling of devices running the HP/Compaq Insight Management Agents. It also contains hardware identification for HP proprietary hardware. The information is collected through the SNMP interface. The following information is modeled. * Hardware Model * Hardware Serial Number * Operating System * CPU Information (socket, speed, cache)
Usage To collect JMX notifications you must edit $ZENHOME/etc/zenjmxnotificationlistener.conf. This file must be used to specify which JMX agents to connect to, and what notifications to collect. After modifying this file you must run ``zenjmxnotificationlistener restart`` for the changes to be affected. Upon installing the ZenPack a default ``zenjmxnotificationlistener.conf`` will be created with the following contents. monitorName=localhost heartbeatInterval=60 heartbeatTimeout=75 connectionRetryInterval=10 xmlRpcUrl=http://localhost:8081/zport/dmd/ZenEventManager xmlRpcUsername=admin xmlRpcPassword=zenoss serverList=LOCALHOST server.LOCALHOST.zenossDevice=localhost server.LOCALHOST.url=service:jmx:rmi:///jndi/rmi://localhost:54107/jmxrmi The scope and attributeFilters properties are optional, and can be used to restrict the notifications captured from a given server. MBeanServerNotification type notifications are ignored by default as they are noisy and unlikely to be useful.
ZenPacks.zenoss.LDAPMonitor monitors the response time of an LDAP server (in milliseconds).
This ZenPack allows for monitoring of memcached. See the Usage section for details on what is monitored. This ZenPack previously existed as a commercial-only extension to Zenoss called ZenPacks.zenoss.MemcachedMonitor. Upon being released as open source its name was changed to better match today's standards. There already exists a very good community ZenPack for memcached by braudel. As far as I can see there is no compelling reason to use this version over that. Ultimately I'd like to see the ZenPacks come together to reduce confusion. At the time that this ZenPack was originally written, the community version didn't exist.