plone

ZenPacks.zenoss.RabbitMQ-4.2.5_1.0.7-2.lbn19.noarch
To start monitoring your RabbitMQ server you will need to setup SSH access so that your Zenoss collector server will be able to SSH into your RabbitMQ server(s) as a user who has permission to run the rabbitmqctl command. This almost always means the root user. See the Using a Non-Root User section below for instructions on allowing non-root users to run rabbitmqctl. To do this you need to set the following zProperties for the RabbitMQ devices or their device class in Zenoss. * zCommandUsername * zCommandPassword * zKeyPath The zCommandUsername property must be set. To use public key authentication you must verify that the public portion of the key referenced in zKeyPath is installed in the ~/.ssh/authorized_keys file for the appropriate user on the RabbitMQ server. If this key has a passphrase you should set it in the zCommandPassword property. If you'd rather use password authentication than setup keys, simply put the user's password in the zCommandPassword property. You should then add the zenoss.ssh.RabbitMQ modeler plugin to the device, or device class containing your RabbitMQ servers and remodel the device(s). This will automatically find the node, vhosts, exchanges and queues and begin monitoring them immediately for the following metrics. * Node Values o Status - Running or not? Generates event on failure. o Open Connections & Channels o Sent & Received Bytes Rate o Sent & Received Messages Rate o Depth of Send Queue o Consumers o Unacknowledged & Uncommitted Messages * Queue Values o Ready, Unacknowledged & Total Messages o Memory Usage o Consumers There is a default threshold of 1,000,000 messages per queue. This is almost certainly an absurdly high threshold that shouldn't trip in normal systems. However, by clicking into the details of any individual queue you can set the per-queue threshold to a more reasonable value that makes sense for a given queue.
Located in LBN / … / Network Monitoring / BastionLinux 19
ZenPacks.zenoss.RabbitMQ-4.2.5_1.0.7-2.lbn19.noarch
To start monitoring your RabbitMQ server you will need to setup SSH access so that your Zenoss collector server will be able to SSH into your RabbitMQ server(s) as a user who has permission to run the rabbitmqctl command. This almost always means the root user. See the Using a Non-Root User section below for instructions on allowing non-root users to run rabbitmqctl. To do this you need to set the following zProperties for the RabbitMQ devices or their device class in Zenoss. * zCommandUsername * zCommandPassword * zKeyPath The zCommandUsername property must be set. To use public key authentication you must verify that the public portion of the key referenced in zKeyPath is installed in the ~/.ssh/authorized_keys file for the appropriate user on the RabbitMQ server. If this key has a passphrase you should set it in the zCommandPassword property. If you'd rather use password authentication than setup keys, simply put the user's password in the zCommandPassword property. You should then add the zenoss.ssh.RabbitMQ modeler plugin to the device, or device class containing your RabbitMQ servers and remodel the device(s). This will automatically find the node, vhosts, exchanges and queues and begin monitoring them immediately for the following metrics. * Node Values o Status - Running or not? Generates event on failure. o Open Connections & Channels o Sent & Received Bytes Rate o Sent & Received Messages Rate o Depth of Send Queue o Consumers o Unacknowledged & Uncommitted Messages * Queue Values o Ready, Unacknowledged & Total Messages o Memory Usage o Consumers There is a default threshold of 1,000,000 messages per queue. This is almost certainly an absurdly high threshold that shouldn't trip in normal systems. However, by clicking into the details of any individual queue you can set the per-queue threshold to a more reasonable value that makes sense for a given queue.
Located in LBN / … / Zenoss 4 / BastionLinux 19
ZenPacks.zenoss.RPCMonitor-4.2.5_1.1.0-1.lbn13.noarch Located in LBN / … / Zenoss 4 / BastionLinux 13
ZenPacks.zenoss.RPCMonitor-3.2.1_1.0.2-1.lbn13.noarch Located in LBN / … / Network Monitoring / BastionLinux 13
ZenPacks.zenoss.RPCMonitor-5.0.5_1.1.0-1.lbn19.noarch Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.RPCMonitor-4.2.5_1.1.0-1.lbn19.noarch Located in LBN / … / Network Monitoring / BastionLinux 19
ZenPacks.zenoss.RPCMonitor-4.2.5_1.1.0-1.lbn19.noarch Located in LBN / … / Zenoss 4 / BastionLinux 19
ZenPacks.zenoss.WindowsMonitor-4.2.5_1.1.0-2.lbn13.noarch
This package provides the capability to monitor windows systems. The following daemons perform Windows monitoring tasks: zenwin - monitors Windows service processes zeneventlog - imports events from the Windows Event Log into Zenoss zenwinperf - collects performance information from Windows machines
Located in LBN / … / Zenoss 4 / BastionLinux 13
ZenPacks.zenoss.WindowsMonitor-5.0.5_1.1.2dev-4.lbn19.noarch
This package provides the capability to monitor windows systems. The following daemons perform Windows monitoring tasks: zenwin - monitors Windows service processes zeneventlog - imports events from the Windows Event Log into Zenoss zenwinperf - collects performance information from Windows machines
Located in LBN / … / Zenoss 5 / BastionLinux 19
ZenPacks.zenoss.WindowsMonitor-4.2.5_1.1.0-3.lbn19.noarch
This package provides the capability to monitor windows systems. The following daemons perform Windows monitoring tasks: zenwin - monitors Windows service processes zeneventlog - imports events from the Windows Event Log into Zenoss zenwinperf - collects performance information from Windows machines
Located in LBN / … / Network Monitoring / BastionLinux 19

« Previous 10 items Next 10 items » 1 ... 58 59 60 61 62 63

Sections

Search results for zenoss


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