plone

ZenPacks.zenoss.Zentrospect-4.2.5_1.2.0-1.lbn19.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.
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss-ldap-5.0.5_4.0.2-2.lbn19.noarch
zenperfldap start/stop/control
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss-pythoncollector-5.0.5_1.8.0dev-4.lbn19.noarch
zenpython start/stop/control
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss-windoz-5.0.5_1.1.2dev-4.lbn19.noarch
Windows monitoring start/stop/control
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss4-4.2.5-20.lbn19.noarch
Zenoss start/stop/control
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss4-mysqld-4.2.5-20.lbn19.noarch
Zenoss MySQL event server start/stop/control
Located in LBN / … / Zenoss 4 / BastionLinux 19
bastion-monit-zenoss4-zep-4.2.5-20.lbn19.noarch
Zenoss Event Processor control script
Located in LBN / … / Zenoss 4 / BastionLinux 19
lbn.zenoss-4.2.5-13.lbn19.noarch
The core libraries and utilities to support writing ZenPacks etc in Bastion-style - pure Python eggs that are standard Zope product's and auto-registered/removed from ZenPackManager upon start/stop of Zope Application Server. Amongst the many advantages of this approach, these ZenPacks are easily installed without any operator assistance via RPM. This package also monkeypatches a range of dastardly Zenoss foibles.
Located in LBN / … / Zenoss 4 / BastionLinux 19
python-txwinrm-1.1.14-2.lbn19.noarch
At Zenoss we are working on a project to improve the reliability, performance and features of native Windows monitoring. The core of this project is this Python library for asynchronously managing Windows using the WinRM and WinRS services. This library will then be used by Zenoss to do automatic discovery and monitoring the way Zenoss users are used to with some new possibilities. Right now we're trying to get as much real world experience using the library as possible to prove out the reliability and performance improvements we're hoping to achieve. If you have access to Windows servers, you can help! It doesn't even require a Zenoss Core installation as this tool stands alone right now. To use kerberos connections, you will need to download and build the python kerberos module from https://github.com/zenoss/pykerberos. Current Feature Support HTTP Basic authentication WQL queries WinRS typeperf Subscribe to the Windows Event Log Kerberos authentication (domain accounts) Payload encryption (Kerberos connections)
Located in LBN / … / Zenoss 4 / BastionLinux 19
rubygem-zenoss_client-0.6.1-1.lbn19.noarch
This is a wrapper around the Zenoss JSON and REST APIs. For the most things it should feel very familiar to zendmd, but there are some changes do to the merging of the JSON and REST APIs. Please read the API docs for Zenoss and the YARDDoc for this gem (rdoc.info).
Located in LBN / … / Zenoss 4 / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 51 52 53 54 55 56 57 ... 63

Sections

Search results for zenoss


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