Modified items

All recently modified items, latest first.

ZenPacks.zenoss.Microsoft.Windows-4.2.5_2.0.0.beta1-1.lbn13.noarch: This ZenPack provides support for monitoring Microsoft Windows. Monitoring is performed using the Windows Remote Management (WinRM) and Windows Remote Shell (WinRS) to collect Windows Management Instrumentation (WMI) and perfmon data.

ZenPacks.zenoss.Memcached-4.2.5_1.0.0-1.lbn13.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.MSSQLServer-4.2.5_2.0.3-1.lbn13.noarch: MS SQL Server

ZenPacks.zenoss.MSMQMonitor-4.2.5_1.2.1-1.lbn13.noarch: MS Message Queue

ZenPacks.zenoss.MSExchange-4.2.5_2.0.4-1.lbn13.noarch: MS Exchange Monitoring

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

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

ZenPacks.zenoss.JabberMonitor-4.2.5_1.1.0-1.lbn13.noarch

ZenPacks.zenoss.IRCDMonitor-4.2.5_1.1.0-1.lbn13.noarch

ZenPacks.zenoss.IISMonitor-4.2.5_2.0.2-1.lbn13.noarch: IISMonitor collects key metrics from Microsoft IIS. The metrics are collected using Windows Perfmon and require no agent to be installed on the IIS server. The following metrics will be collected and graphed for Microsoft IIS. * Connections Attempts * Throughput (Bytes & Files) * Requests (GET, HEAD, POST, CGI, ISAPI) Standard: GET, HEAD, POST, CGI, ISAPI WebDAV: PUT, COPY, MOVE, DELETE, OPTIONS, PROPFIND, PROPPATCH, MKCOL Other: SEARCH, TRACE, LOCK, UNLOCK Follow these steps to setup your IIS server to have this information collected. 1. Verify that your Zenoss Windows service account has access to the IIS server. Within Zenoss this is specified using zWinUser and zWinPassword. 2. Bind the IIS performance template to the IIS server device within Zenoss.

ZenPacks.zenoss.HttpMonitor-4.2.5_2.1.0-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-4.2.5_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-4.2.5_1.1.0-1.lbn13.noarch

ZenPacks.zenoss.EsxTop-4.2.5_1.1.0-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-4.2.5_2.1.0-1.lbn13.noarch

ZenPacks.zenoss.DigMonitor-4.2.5_1.1.0-1.lbn13.noarch

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

ZenPacks.zenoss.DellMonitor-4.2.5_2.2.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.DRBDMonitor-4.2.5_1.0.0-1.lbn13.noarch

ZenPacks.zenoss.CloudStack-4.2.5_1.0.9-1.lbn13.noarch: The easiest way to start monitoring CloudStack is to navigate to the Infrastructure page, click the *+* menu to add a device and choose Add CloudStack. Fill out the URL, API Key, and Secret Key fields then click OK. The URL should only include the protocol, host and port (i.e. http://cloudstack.example.com/). You can find or create the keys by logging into the CloudStack web interface and navigate to Accounts and users. Zenoss will then add the CloudStack device to the system along with all of its associated zones, pods, clusters, system VMs and VMs. Monitoring will also start after the discovery is complete. Metrics Once you've successfully added a CloudStack cloud to Zenoss you will begin to see the following metrics available for the entire cloud. These numbers are aggregated from all zones, pods, clusters and hosts. Public IPs: Total and Used Private IPs: Total and Used Memory: Total (with and without over-provisioning), Allocated and Used CPU: Total (with and without over-provisioning), Allocated and Used Primary Storage: Total (with and without over-provisioning), Allocated and Used Secondary Storage: Total and Used Network: Read and Write The same list of metrics are available for each zone. The same metrics with the exception of public IPs and secondary storage are also available for each pod. The following metrics are available aggregated to each cluster, and for each host. Memory: Total and Used CPU: Total (with and without over-provisioning), Allocated, Used and Cores Network: Read and Write Events CloudStack has both alerts and events. Once you've successfully added a CloudStack cloud to Zenoss you will automatically receive all CloudStack alerts as events in Zenoss. You will also automatically receive all CloudStack events. However, the events will go straight into your event history by default. To avoid overloading CloudStack and Zenoss, only the last two (2) days of events will be checked. This allows for timezone discrepency between the Zenoss and CloudStack servers as well as some downtime without missing events. There is no real-time event collection mechanism with the CloudStack API, so alerts and events will only be polled once per minute. Installed Items Installing the ZenPack will add the following items to your Zenoss system. Device Classes /CloudStack Configuration Properties zCloudStackURL zCloudStackAPIKey zCloudStackSecretKey Modeler Plugins zenoss.CloudStack Monitoring Templates Cloud Zone Pod Cluster Host Event Classes /Status/CloudStack /Perf/CloudStack /App/CloudStack

« Previous 20 items Next 20 items » 1 ... 2307 2308 2309 2310 2311 2312 2313 ... 2425


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

Sections

Modified items