plone

ZenPacks.zenoss.ZenJMX-3.2.1_3.5.3-1.lbn13.x86_64
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).
Located in LBN / … / Network Monitoring / BastionLinux 13
ZenPacks.zenoss.ZenossVirtualHostMonitor-3.2.1_2.3.6-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)
Located in LBN / … / Network Monitoring / BastionLinux 13
bastion-monit-zenoss-3.2.1-1.lbn13.noarch
BastionLinux monit services configuration and control scripts for Zenoss 3.
Located in LBN / … / Network Monitoring / BastionLinux 13
bastion-monit-zenoss-mysqld-3.2.1-1.lbn13.noarch
Zenoss/mysql start/stop/control
Located in LBN / … / Network Monitoring / BastionLinux 13
lbn.recipe.zenoss-1.0.1-1.lbn13.noarch Located in LBN / … / Network Monitoring / BastionLinux 13
lbn.recipe.zenoss-egginfo-1.0.1-1.lbn13.noarch
easy_install egg information
Located in LBN / … / Network Monitoring / BastionLinux 13
lbn.zenoss-3.0.8-1.lbn13.noarch
The core libraries and utilities to support writing ZenPacks etc in Bastion-style.
Located in LBN / … / Network Monitoring / BastionLinux 13
chef-handler-zenoss-0.0.4-1.lbn19.noarch
Allows reporting of Chef run metrics from Zenoss event console. You'll need the chef_handler recipe and something like the following in a recipe of your own: chef_handler 'Chef::Handler::ZenossHandler' do action :enable arguments [node[:zenoss][:server_url], node[:zenoss][:server_username], node[:zenoss][:server_password] ] source ::File.join(::Gem.all_load_paths.grep(/chef-handler-zenoss/).first, 'chef', 'handler', 'zenoss') end
Located in LBN / … / Core Linux / BastionLinux 19
ZenPacks.lbn.LDAPMonitor-4.2.4_4.0.2-1.lbn13.noarch
LDAPMonitor ----------- LDAPMonitor provides a method for pulling performance metrics from any LDAP server which implements the cn=Monitor standard. The monitor works by directly querying the LDAP server using the configured user dn and password credentials. Make sure that your LDAP server is available from your Zenoss console, you've enabled cn=monitor on it, and that the user has sufficient permissions to perform a 'cn=snmp,cn=monitor' search. The following metrics will be collected and graphed for the LDAP Server: * Operations o Add Entry o Modify Entry o Delete Entry o Search Entry * Bindings o Anonymous o Simple Auth o Unauthorised * Errors o Bind Security o Security o Other Errors o Failures * Response Time * Referrals You can add LDAP monitoring to the device within Zenoss by simply binding the LDAPMonitor template to the device. 1. Navigate to the device in the Zenoss web interface. 2. Click the device menu, choose More then Templates. 3. Click the templates menu, choose Bind Templates. 4. Ctrl-click the LDAPMonitor template from /Devices/Server to choose it. 5. Click OK. You will now be collecting the LDAP Server metrics from this device.
Located in LBN / … / Access and Identity Management / BastionLinux 13
bastion-monit-zenoss-ldap-4.2.4_4.0.2-1.lbn13.noarch
zenperfldap start/stop/control
Located in LBN / … / Access and Identity Management / BastionLinux 13

« Previous 10 items Next 10 items » 1 ... 42 43 44 45 46 47 48 ... 63

Sections

Search results for zenoss


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