Modified items

All recently modified items, latest first.

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-utils-4.2.5-1.1.lbn25.noarch: Java utility packages for Zenoss/ZEP

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-parent-4.2.5-1.5.lbn25.noarch: Parent POM file for Zenoss Specs.

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.NNTPMonitor-4.2.5_1.1.0-1.lbn25.noarch

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.JabberMonitor-4.2.5_1.1.0-1.lbn25.noarch

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.IRCDMonitor-4.2.5_1.1.0-1.lbn25.noarch

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.

ZenPacks.zenoss.Docker-4.2.5_1.1.0-1.lbn25.noarch: Adds modeler plugin and monitoring datasource to retrieve list of Docker containers and monitor their statuses. Docker Containers modeled in Zenoss device

ZenPacks.zenoss.DigMonitor-4.2.5_1.1.1-1.lbn25.noarch

ZenPacks.zenoss.DeviceSearch-4.2.5_1.2.0-1.lbn25.noarch

ZenPacks.zenoss.DellMonitor-4.2.5_2.2.0-1.lbn25.noarch: DellMonitor provides custom modeling of devices running the Dell OpenManage agents. It also contains hardware identification for Dell 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, voltage) * PCI Card Information (manufacturer, model)

ZenPacks.zenoss.ApacheMonitor-4.2.5_2.1.4-1.lbn25.noarch: ApacheMonitor ------------- ApacheMonitor provides a method for pulling performance metrics from the Apache HTTP Server (http://httpd.apache.org/) directly into Zenoss without requiring the use of an agent. This is accomplished by utilizing the standard mod_status module that comes with version 1 and 2 of the HTTP server. The following metrics will be collected and graphed for the Apache HTTP Server. * Requests per Second * Throughput (Bytes/sec & Bytes/request) * CPU Utilization of the HTTP server and all worker processes/threads * Slot Usage (Open, Waiting, Reading Request, Sending Reply, Keep-Alive, DNS Lookup and Logging) Follow these steps to setup your HTTP server so that it will allow Zenoss to access the server status. 1. On the Apache server, find your httpd.conf file. This is normally located in /etc/httpd/httpd.conf or /etc/httpd/conf/httpd.conf. Other locations are possible depending on your operating system and setup. 2. Turn the ExtendedStatus option on in the httpd.conf file. This option will typically be commented out. You can enable it by uncommenting it. ... becomes ... ExtendedStatus on 3. Enable the /server-status location in the httpd.conf file. This is another option that typically already exists but is commented out. ... becomes ... <Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from zenoss.yourdomain.com </Location> 4. Save the httpd.conf file with these changes then restart httpd. This can normally be accomplished with following command. apachectl restart Once your Apache HTTP Server is configured to allow Zenoss to access the extended status, you can add Apache monitoring to the device within Zenoss by simply binding the Apache template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the Apache template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Apache HTTP Server metrics from this device.

« Previous 20 items Next 20 items » 1 ... 1823 1824 1825 1826 1827 1828 1829 ... 2437


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

Sections

Modified items