Search results for zenoss

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

Xen Monitor --------------------------- XenMonitor is a ZenPack that allows you to monitor virtually hosted operating systems running on a Xen hypervisor. It depends on the prior installation of the ZenossVirtualHostMonitor zenpack. This zenpack: 1) Extends ZenModeler to find Guest OS's and add them to Virtual Hosts 3) Provides templates for collecting resources allocated to Guest OSs. To Use XenMonitor: 1) Ensure that you have SSH keys to your Xen servers (as root). 2) Create your Xen servers using the /Servers/Virtual Hosts/Xen device class. If you have these servers modeled already, remove them and recreate them under the Xen device class. DO NOT MOVE THEM. 3) Select the Guest menu and ensure that the guest hosts were found when the devices were added.

ZenPacks.zenoss.ZenJMX-4.2.3_3.9.3-6.lbn13egg.noarch

ZenJMX is a full-featured JMX client that works "out of the box" with JMX agents that have their remote APIs enabled. It supports authenticated and unauthenticated connections, and it can retrieve single-value attributes, complex-value attributes, and the results of invoking an operation. Operations with parameters are also supported so long as the parameters are primitive types (Strings, booleans, numbers), as well as the object version of primitives (such as java.lang.Integer and java.lang.Float). Multi-value responses from operations (Maps and Lists) are supported, as are primitive responses from operations. The JMX data source installed by ZenJMX allows you to define the connection, authentication, and retrieval information you want to use to retrieve performance information. The IP address is extracted from the parent device, but the port number of the JMX Agent is configurable in each data source. This allows you to operate multiple JMX Agents on a single device and retrieve performance information for each agent separately. This is commonly used on production servers that run multiple applications. Authentication information is also associated with each JMX data source. This offers the most flexibility for site administrators because they can run some JMX agents in an open, unauthenticated fashion and others in a hardened and authenticated fashion. SSL-wrapped connections are supported by the underlying JMX Remote subsystem built into the JDK, but were not tested in the Zenoss labs. As a result, your success with SSL encrypted access to JMX Agents may vary. The data source allows you to define the type of performance information you want to achieve: single-value attribute, complex-value attribute, or operation invocation. To specify the type of retrieval, you must specify an attribute name (and one or more data points) or provide operation information. Any numerical value returned by a JMX agent can be retrieved by Zenoss and graphed and checked against thresholds. Non-numerical values (Strings and complex types) cannot be retrieved and stored by Zenoss. When setting up data points, make sure you understand the semantics of the attribute name and choose the correct Zenoss data point type. Many JMX Agent implementations use inconsistent nomenclature when describing attributes. In some cases the term "Count" refers to an ever-increasing number (a "Counter" data point type). In other cases the term "Count" refers to a snapshot number (a "Gauge" data point type).

ZenPacks.zenoss.ZenossVirtualHostMonitor-4.2.5_2.4.0-1.lbn13.noarch

Zenoss Virtual Host Monitor --------------------------- ZenossVirtualHostMonitor is a ZenPack that allows you to monitor virtually hosted operating systems. This ZenPack refers to a Virtual Machine Host as the one running on the bare metal, and Guest for those running within the virtual hardware. This zenpack: 1) Extends Devices to support a relationship from Host to Guest. 2) Provides screens displaying resources allocated to Guest OSs. 3) Collects nothing on its own. It provides base functionality for other zenpacks (XenMonitor, VMwareESXMonitor)

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

Features The features added by this ZenPack can be summarized as follows. They are detailed further below. Discovery of Zenoss systems, processes and metrics thereof. Monitoring of process metric values. Monitoring of process metric freshness. Discovery The following entities will be automatically discovered from server devices that are running Zenoss, have the zenoss.snmp.ZenossSNMP modeler plugin assigned, and have the zenoss-snmp-module extension to Net-SNMP installed and configured properly. Zenoss Systems Attributes: Name Collections: Zenoss Processes, Zenoss Metrics Zenoss Processes Attributes: Name, System Collections: Zenoss Metrics Zenoss Metrics Attributes: Name, System, Process Monitoring The following metrics will be collected every 5 minutes by default. Metrics Metrics: zenProcessMetricValue, zenProcessMetricCyclesSinceUpdate zenProcessMetricValue is the most recent value recorded for the metric. It will be NaN in cases where a value hasn't been recorded recently. zenProcessMetricCyclesSinceUpdate is how many "cycle intervals" it has been since the value was successfully recorded. This measure is used because some metrics are updated on different cycle intervals. For example, if the localhost-zenperfsnmp-devices metric is updated every 300 seconds and was last updated 30 seconds ago, the zenProcessMetricCyclesSinceUpdate value will be 0.1. By default a maximum threshold of 2 is set for zenProcessMetricCyclesSinceUpdate on all discovered metrics. This can be used to identify Zenoss processes that are not functioning properly. Service Impact When combined with the Zenoss Service Dynamics product, this ZenPack adds service impact capability for the entities it discovers. The following service impact relationships are automatically added. These will be included in any services that contain one or more of the explicitly mentioned entities. Service Impact Relationships A Device failure impacts all associated Zenoss Systems. A Zenoss System failure impacts all associated Zenoss Processes. A Zenoss Process failure impacts all associated Zenoss Metrics.

bastion-monit-zenoss-ldap-4.2.4_4.0.2-1.lbn13.noarch

zenperfldap start/stop/control

bastion-monit-zenoss-pythoncollector-4.2.5_1.6.0-4.lbn13.noarch

zenpython start/stop/control

bastion-monit-zenoss-windoz-4.2.4_1.0.8-2.lbn13.noarch

Windows monitoring start/stop/control

bastion-monit-zenoss4-4.2.5-3.lbn13.noarch

Zenoss start/stop/control

bastion-monit-zenoss4-mysqld-4.2.5-3.lbn13.noarch

Zenoss MySQL event server start/stop/control

bastion-monit-zenoss4-zep-4.2.5-3.lbn13.noarch

Zenoss Event Processor control script