plone

ZenPacks.zenoss.JMXNotificationListener-5.0.5_0.9.1-5.lbn19.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.
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.JabberMonitor-5.0.5_1.1.0-1.lbn19.noarch Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.LDAPMonitor-5.0.5_1.4.1-1.lbn19.noarch
ZenPacks.zenoss.LDAPMonitor monitors the response time of an LDAP server (in milliseconds).
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.LinuxMonitor-5.0.5_1.3.0-1.lbn19.noarch
This ZenPack provides RRD templates and command parsers for monitoring Linux hosts.
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.Memcached-5.0.5_1.0.0-1.lbn19.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.
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.Microsoft-5.0.5_2.5.0dev-2.lbn19.noarch
ZenPacks.zenoss.Microsoft.Windows module
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.Microsoft.Windows-5.0.5_2.5.0dev-2.lbn19.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.
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.NNTPMonitor-5.0.5_1.1.0-1.lbn19.noarch Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.NtpMonitor-5.0.5_2.3.0dev-1.lbn19.noarch Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.OpenStackInfrastructure-5.0.5_2.1.1dev-1.lbn19.noarch
This ZenPack allows for monitoring of OpenStack from a service provider perspective. This means that in addition to the user-oriented components supported in the regular OpenStack ZenPack (instances, flavors, images), the underlying OpenStack servers and software are monitored. Once the OpenStack ZenPack is installed and you can begin monitoring by going to the infrastructure screen and clicking the normal button for adding devices. You'll find a new option labeled, "Add OpenStack Endpoint (Infrastructure)." Choose that option and you'll be presented with a dialog asking for the following inputs. Device To Create - name to use for this device in zenoss. Should not be an actual hostname, since that name will be used when the host is registered as a linux device. Auth URL - A keystone URL, such as http://<hostname>:5000/v2.0/ Username, Password / API Key, Project/Tenant ID - *Administrative* credentials to your zenoss instance. Region Name - choose the correct region from the dropdown. You may only choose one, so each region you wish to manage must be registered as a separate endpoint in zenoss. Ceilometer URL - Will auto-populate based on the other selections. Once you click Add, Zenoss will contact the OpenStack API and discover servers, images and flavors. Once it is complete you'll find a new device in the OpenStack device class with the same name as the hostname or IP you entered into the dialog. Click into this new device to see everything that was discovered. The following types of elements are discovered. Tenants Instances (Servers) vNICs Images Flavors Nova API Endpoints Regions Availability Zones Hosts Nova Services (processes supporting nova servers) Hypervisors The following component level metrics are collected. Instances CPU Utilization (percent) Disk Requests (requests/sec) Disk IO Rate (bytes/sec) Vnics Network Packet Rate (packets/sec) Network Throughput (bytes/sec) Hosts (Zenoss Linux OS monitoring) Load Average (processes) CPU Utilization (percent) Free Memory (bytes) Free Swap (bytes) IO (sectors/sec) Nova Services (Zenoss Process monitoring) CPU Utilization (percent) Memory Utilization (bytes) Process Count (processes) The following device level metrics are collected. Flavors Total (count) Images Total (count) Total count per image state (count) Servers Total (count) Total count per server state (count) Queues Event (count) Performance (count)
Located in LBN / … / Zenoss 5 / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 2425 2426 2427 2428 2429 2430 2431 ... 4852

Sections

Search results


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