Modified items

All recently modified items, latest first.

zenoss-zep-rdbms-4.2.5-12.lbn25.noarch: Scripts/dependencies for setting up RDBMS backend/s for ZEP

zenoss-zep-pgsql-4.2.5-12.lbn25.noarch: This package sets up the postgresql backend for Zenoss/ZEP. The root is automatically set to accept as a remote user.

zenoss-zep-parent-4.2.5-1.5.lbn25.noarch: Parent POM file for Zenoss ZEP Specs.

zenoss-zep-oracle-4.2.5-12.lbn25.noarch: This package sets up the oracle backend for Zenoss/Zentinel. The root is automatically set to accept as a remote user.

zenoss-zep-mysql-4.2.5-12.lbn25.noarch: The root is automatically set to accept as a remote user.

zenoss-zep-4.2.5-12.lbn25.noarch: Zenoss Event Processor This package also sets up/coordinates the necessary jar file dependencies for this Jetty server/application.

zenoss-protobuf-python-0.2-6.lbn25.noarch: Python implementation of Zenoss Protocols

zenoss-protobuf-java-1.2.2_SNAPSHOT-6.lbn25.noarch: Java implementation of Zenoss Protocols

zenoss-protobuf-4.2.5-6.lbn25.noarch: Zenoss ZenEventPer and Impact protocol connectors

zenoss-jars-4.2.5-1.13.lbn25.noarch: Maven is a complete crock of shite and we are still figuring out how to build some critical dependency versions that may not be at the same point release as distro mainline. We are simply deploying the expected versions here.

ZenPacks.zenoss.Memcached-4.2.5_1.0.0-1.lbn25.noarch: 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.

ZenPacks.zenoss.LDAPMonitor-4.2.5_1.4.1-1.lbn25.noarch: ZenPacks.zenoss.LDAPMonitor monitors the response time of an LDAP server (in milliseconds).

ZenPacks.zenoss.JMXNotificationListener-4.2.5_0.9.1-5.lbn25.noarch: 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.HPMonitor-4.2.5_2.1.0-1.lbn25.noarch: 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)

ZenPacks.zenoss.EsxTop-4.2.5_1.1.1-1.lbn25.noarch: 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.


	Copyright © 2000-2024 Corporation of Balclutha Inc. All rights reserved.