You are here: Home / LBN / Up2date / Network Monitoring / BastionLinux 19 / ZenPacks.zenoss.Zentrospect-4.2.5_1.2.0-1.lbn19.noarch

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

Package Attributes
RPM  ZenPacks.zenoss.Zentrospect-4.2.5_1.2.0-1.lbn19.noarch.rpm Architecture  noarch Size  114755 Created  2019/09/30 06:52:37 UTC
Package Specification
Summary Monitoring Zenoss servers using zenoss-snmp-module.
Group Zenoss
License GPL
Home Page http://www.zenoss.com
Description

Features

Discovery of Zenoss systems, processes and metrics thereof. Monitoring of process metric values. Monitoring of process metric freshness.

The features added by this ZenPack can be summarized as follows. They are detailed further below.

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.

Requires
rpmlib(FileDigests)  
rpmlib(PartialHardlinkSets)  
rpmlib(CompressedFileNames)  
rpmlib(PayloadFilesHavePrefix)  
/bin/sh  
rpmlib(PayloadIsXz)  
zenoss4  
Provides
ZenPacks.zenoss.Zentrospect

Document Actions