Accelerate Your Path to Full-Stack Monitoring and Alerting
Register for this live webinar featuring Zenoss and VictorOps today!
Why Customers Choose Us
Discover why the largest companies in the world choose Zenoss.
Customer Support Portal
Zenoss Learning Center
Zenoss Partner Portal
Become a Partner
Top 5 Focus Areas to Succeed With DevOps
Forrester shares the tools, technologies and best practices to meet the challenges of today's modern IT environments.
Learn. Discuss. Participate.
Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Hybrid IT Monitoring
Zenoss provides complete visibility into physical, virtual, cloud and converged environments.
Request A Demo
Note: This Zenpack has been merged and replaced by the Linux Monitor ZenPack
This ZenPack is included with commercial versions of Zenoss and enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.
The ZenPacks.zenoss.EnterpriseLinux ZenPack extends the capabilities of ZenPacks.zenoss.LinuxMonitor and enables Zenoss platform to use Secure Shell (SSH) to monitor Linux hosts.
Zenoss platform models and monitors devices placed in the /Server/SSH/Linux device class by running commands and parsing the output. Parsing of command output is performed on the Zenoss platform server or on a distributed collector. The account used to monitor the device does not require root access or special privileges for the default modeler plugins.
The following procedure assumes that the credentials have been set.
All Linux servers must have a device entry in an organizer below the /Devices/Server/SSH/Linux device class.
Tip: The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.
The zencommand daemon's log file ($ZENHOME/collector/zencommand.log) may show messages stating:
ERROR zen.SshClient CHANNEL_OPEN_FAILURE: Authentication failure
WARNING:zen.SshClient:Open of command failed (error code 1): open failed
If the sshd daemon's log file on the remote device is examined, it may report that the MAX_SESSIONS number of connections has been exceeded and that it is denying the connection request. At least in the OpenSSH daemons, this MAX_SESSIONS number is a compile-time option and cannot be reset in a configuration file.
In order to work around this limitation of the sshd daemon, use the configuration property zSshConcurrentSessions to control the number of connections created by zencommand to the remote device.
WARNING:zen.zencommand:Command timed out on device device_name: command
If this occurs, it usually indicates that the remote device has taken too long to return results from the commands. To increase the amount of time to return results, change the configuration property zCommandCommandTimeout to a larger value.
This plugin allows you to collect and model detailed hardware and kernel information on your Linux devices.
Since the dmidecode command requires root privileges, it needs to be run with something like sudo. Sample entries required on the sudoers file on each remote device are:
Cmnd_Alias DMIDECODE = /usr/sbin/dmidecode
## Allows members of the zenoss group to gather modeling information
%zenoss ALL = (ALL) NOPASSWD: DMIDECODE
To use this plugin, add it to the list of collector plugins for the device or device class, and then remodel. For more information about working with Zenoss platform plugins, refer to Zenoss Service Dynamics Resource Management Administration.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Commercial ZenPacks are available to Zenoss commercial customers only. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Commercial ZenPacks.