Modified items

All recently modified items, latest first.

ZenPacks.zenoss.NNTPMonitor-3.2.1_1.0.2-1.lbn13.noarch

ZenPacks.zenoss.MySqlMonitor-3.2.1_2.1.3-1.lbn13.noarch: MySqlMonitor provides a method for pulling performance metrics from the MySQL database server (http://www.mysql.com/) directly into Zenoss without requiring the use of an agent. This is accomplished by utilizing the MySQL client library to connect to the database remotely. The following metrics will be collected and graphed for MySQL server. * Command Statistics (SELECT, INSERT, UPDATE, DELETE) * Select Statistics (Scan, Range Check, Range Join, Full Join) * Handler Statistics (Keyed & Unkeyed Reads, Writes, Updates, Deletes) * Network Traffic (Received & Sent)

ZenPacks.zenoss.LinuxMonitor-3.2.1_1.1.5-1.lbn13.noarch: This ZenPack provides RRD templates and command parsers for monitoring Linux hosts.

ZenPacks.zenoss.JabberMonitor-3.2.1_1.0.2-1.lbn13.noarch

ZenPacks.zenoss.IRCDMonitor-3.2.1_1.0.2-1.lbn13.noarch

ZenPacks.zenoss.HttpMonitor-3.2.1_2.0.3-1.lbn13.noarch: ZenPacks.zenoss.HttpMonitor monitors connection response time to an HTTP server and determines whether specific content exists on a Web page.

ZenPacks.zenoss.HPMonitor-3.2.1_2.1.0-1.lbn13.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.FtpMonitor-3.2.1_1.0.2-1.lbn13.noarch

ZenPacks.zenoss.EsxTop-3.2.1_1.0.3-1.lbn13.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.DnsMonitor-3.2.1_2.0.2-1.lbn13.noarch

ZenPacks.zenoss.DigMonitor-3.2.1_1.0.2-1.lbn13.noarch

ZenPacks.zenoss.DellMonitor-3.2.1_2.1.0-1.lbn13.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-3.2.1_2.1.2-1.lbn13.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.

ZenPacks.zenoss-1.0.0-1.lbn13.noarch: Zenoss ZenPack module

ZenPacks.oie.KannelMonitor-3.2.1_3.0.0-3.lbn13.noarch: KannelMonitor ------------- KannelMonitor uses the nagios check-kannel plugin to retrieve input queue and delivery volumes from any Kannel-based SMPP server. Once your Kannel Server has the check-kannel plugin installed, you can add Kannel monitoring to the device within Zenoss by simply binding the KannelMonitor 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 KannelMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Kannel Server metrics from this device.

ZenPacks.lbn.ZopeMonitor-3.2.1_3.0.1-1.lbn13.noarch: ZopeMonitor ------------- ZopeMonitor provides a method for pulling performance metrics from a Zope Application Server (http://www.zope.org/) directly into Zenoss. It is necessary to first install the munin.zope eggs from pypi.python.org or our own repo at http://linux.last-bastion.net/LBN/up2date/monitor, and to have wget installed on this server. The monitor works by utilising ZenCommand to run wget on the local system - you do not need to make zope ports available through your firewall. The munin plugins do require a user with 'View Management Screens' access at the root however. This is configured using the zZopeURI zProperty of the device. This parameter uses Extended HTTP Authentication to specify user credentials, host and port. Note that the host is the hostname on the remote instance and should probably remain 'localhost' unless you've explicitly bound your Zope to a NIC. Note that the munin plugins expect to be installed on a Unix-like operating system with a /proc filesystem. The following metrics will be collected and graphed for the Zope Server. * Threads o Free threads o Total threads * Cache o Total objects o Total objects in memory o Targe number * ZODB Activity o Total connections o Total load count o Total store count * Memory Utilisation o VmHWM - peak resident set size ("high water mark") o VmExe - size of text segments o VmStk - size of stack segments o VmPeak - peak virtual memory size o VmData - size of data segments o VmLck - locked memory size o VmPTE - page table entries size o VmLib - shared library code size o VmRSS - resident set size Once your Zope Server has the munin plugins installed, you can add Zope monitoring to the device within Zenoss by simply binding the ZopeMonitor 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 ZopeMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the Zope Server metrics from this device.

ZenPacks.lbn.ZenSlave-1.0.6-1.lbn13.noarch: ZenSlave is a collector which allows you to set up and send local device performance statistics to a remote ZenMaster.

ZenPacks.lbn.ZenMaster-1.0.6-1.lbn13.noarch: ZenMaster is a collector which allows you to set up and control remote ZenSlave performance statistics.

ZenPacks.lbn.Base-3.2.1_3.0.1-5.lbn13.noarch: Last Bastion Network product information into your Zenoss Server, and all the necessary monkey patches to your Zope environment.

ZenPacks.community.libvirt-1.96-1.lbn13.noarch: This ZenPack leverages the libvirt API for monitoring virtualization servers (e.g. XEN, KVM, etc...). This uses the system python and libvirt python API to monitor various virtualization platforms remotely. It provides a /Server/libvirtHost device class and this module is tested using ssh as a transport for the libvirt API, it could be made to use TLS or TCP with further development. It provides a libvirtvirtualHostlist report as well. You can set zLibvirtUsername and zLibvirtConnectType to customize access to the hosts, though only qemu+ssh:// was tested at the moment. libvirt supports: * The Xen hypervisor on Linux and Solaris hosts. * The QEMU emulator * The KVM Linux hypervisor * The LXC Linux container system * The OpenVZ Linux container system * The User Mode Linux paravirtualized kernel * The VirtualBox hypervisor * The VMware ESX and GSX hypervisors * Storage on IDE/SCSI/USB disks, FibreChannel, LVM, iSCSI, NFS and filesystems

« Previous 20 items Next 20 items » 1 ... 2350 2351 2352 2353 2354 2355 2356 ... 2359


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

Sections

Modified items