Life With Zenoss Cloud Gives You Intelligent Insights
EXPLORE THE PLATFORM
Life With Zenoss Cloud Gives You ControlPrevent IT Outages and Predict Issues
Life With Zenoss Cloud Gives You Massive Scale
Zenoss Partner Portal
Become a Partner
Learn. Discuss. Participate.Join thousands of Zenoss users and experts to learn, discuss and participate in the Zenoss Community.
Customer Support Portal
Zenoss Learning Center
Analyst ReportForrester: Top 5 Focus Areas to Succeed With DevOps
Customers for LifeAt Zenoss, our customers are at the core of everything we do.
Request A Demo
This ZenPack monitors the Linux Operating System.
This ZenPack provided monitoring support for Linux, leveraging OpenSSH for data access. In addition to system health, disks, LVM, services, and processes are monitored.
This version of LinuxMonitor fully replaces EnterpriseLinux. To avoid related errors in zenhub logs, EnterpriseLinux ZP should be removed after the new LinuxMonitor has been applied.
The following entities will be automatically discovered. The attributes and collections will be updated on Zenoss normal remodeling interval which defaults to every 12 hours.
Some links between server and client of NFS File System and other storage devices are intentionally removed as they significantly impact performance.
Prior to version 2.3.0, some columns (Loaded Status, Processes, Description) may be empty. These columns are removed in version 2.3.0
All Linux servers must have a device entry in an organizer below the /Devices/Server/SSH/Linux device class.
The SSH monitoring feature will attempt to use key-based authentication before using a configuration properties password value.
This ZenPack requires the ability to run the pvs, vgs, lvs, systemctl, initctl and service commands, remotely on your linux server(s) using SSH. By default, these commands are only allowed to be run locally. To remotely run these commands, the root user must not be required to use TTY.
Install the sudo package on your server.
Allow root user to execute commands via ssh without a TTY.
Edit the /etc/sudoers file.
Find the line containing root ALL=(ALL) ALL.
Add this line underneath it:
Save the changes and exit.
This ZenPack requires the ability to run the pvs, vgs, lvs, systemctl, initctl, df and service commands, remotely on your linux server(s) using SSH. By default, most of these commands are only allowed to be run by the root user. The output of systemctl, initctl, df and service commands depends on whether they are executed via sudo. Furthermore, this ZenPack expects these commands be in the user's path. Normally this is only true for the root user.
Assuming that you've created a user named zenmonitor on your linux servers for monitoring purposes, you can follow these steps to allow the zenmonitor user to run the commands.
Install the sudo package on your server
Allow the zenmonitor user to run the commands via ssh without a TTY
Edit /etc/sudoers.d/zenoss (Or /etc/sudoers if sudoers.d not supported) and add the following lines to the bottom of the file:
Cmnd_Alias ZENOSS_LVM_CMDS = /sbin/pvs, /sbin/vgs, /sbin/lvs, \
/usr/sbin/pvs, /usr/sbin/vgs, /usr/sbin/lvs
Cmnd_Alias ZENOSS_SVC_CMDS = /bin/systemctl list-units *, \
/bin/systemctl show *, /sbin/initctl list, /sbin/service *, \
/sbin/runlevel, /usr/sbin/dmidecode, /bin/ls -l /etc/rc?.d/
Cmnd_Alias ZENOSS_NET_CMDS = /bin/dmesg
Cmnd_Alias ZENOSS_DF_CMDS = /bin/df
zenmonitor ALL=(ALL) NOPASSWD: ZENOSS_LVM_CMDS, ZENOSS_SVC_CMDS, ZENOSS_NET_CMDS, ZENOSS_DF_CMDS
Save, ensuring all paths for these commands are correct
In order for Ssh operation works correctly, ensure OpenSSH is updated to your distro's current version. This is especially true for older versions of RHEL, CentOS, Ubuntu, and SUSE Linux.
If using a non-root user on SUSE Linux you must set the following as root due to SUSE restricting dmesg.
echo 0 > /proc/sys/kernel/dmesg_restrict
For SUSE Linux the paths for (pvs, vgs, lvs) are located at /sbin/pvs, /sbin/vgs, and /sbin/lvs respectively. Please ensure that each command can be manually executed remotely.
Table: Linux Configuration Properties
zSshConcurrentSessions property by default equals to 5. In case of increasing this value user has change sshd daemon configuration on target device by increasing allowed session number and restart sshd daemon.
The following procedure assumes that credentials have been set.
Select Infrastructure from the navigation bar.
Select Add a Single Device from the Add Device list of options. The Add a Single Device dialog appears.
Enter the following information in the dialog:
Table: Adding Linux Device Details
Alternatively you can use zenbatchload to add Linux servers from the command line. To do this, you must create a text file with hostname, username and password of all the servers you want to add. Multiple endpoints can be added under the same /Devices/Server/Linux section. Here is an example...
LinuxDevice zCommandUsername="user", zCommandPassword="password"
You can then load the Linux servers into Zenoss Core or Resource Manager as devices with the following command.
The Linux OS services are modeled using the zenoss.cmd.linux.os_service modeler plugin. The following systems are supported:
Version 2.3.0 supports monitoring of the status of systemd, upstart and systemV system services. OSService-SYSTEMD, OSService-UPSTART and OSService-SYSTEMD monitoring templates are automatically bound to a service component based on the targets modeled init system value. The zProperties zLinuxServicesModeled and zLinuxServicesNotModeled restrict the services that are modeled and thereby monitored.
For systemd, only services that are enabled (or have "enabled-runtime" status). Futhermore, oneshot services or services with unmet conditions are not modeled or monitored. In order to prevent a service from being modeled and monitored by Zenoss, the service will have to be stopped and disabled. One of those actions alone won't be sufficient. Another way to prevent a service from modeling is to add it to the zLinuxServicesNotModeled zProperty. To also model active services of any UnitFileState (enabled, disabled, static, etc.), the zLinuxModelAllActiveServices zProperty should be set to True.
Upstart devices monitor all enabled services managed by upstart and additionally also monitors systemV services that run in the current runlevel of the same device. The Init System property, found in the Details menu of the service, displays which init system the service is managed by.
SystemV devices model and monitor all services in the current runlevel.
zLinuxServiceModeled and zLinuxServiceNotModeled can support multiple regex expressions when separated on new lines. Although the zLinuxModelAllActiveServices property models all active services that are also disabled when checked, this property will still not model onseshot services or those services whose conditions are not met. The OSService monitoring template generates events on every collection cycle for a service that is down. The events are automatically cleared if the service is up again.
zLinuxServicesNotModeled overrules zLinuxServicesModeled. If a service name matches regexes in both zProperties, the service will not modeled.
Installing this ZenPack will add the following items to your Zenoss system.
As of version 2.3.0 the zenoss.cmd.linux.rpm and zenoss.cmd.linux.alt_kernel_name modeler plugins are disabled by default on new installs. If upgrading from a version previous to 2.3.0 they will still be enabled by default. It is recommended you disable the modeler plugin zenoss.cmd.linux.alt_kernel_name if you have a customized /etc/issue file as customization could affect modeling results.
Device (in /Devices/Server/SSH/Linux)
In version 2.3.0 support for the datapoints MemAdjustedUsed and MemAdjustedUsedPercent were added. Theses datapoints include Buffers, Cached and Free in the memory used calculation. These datapoints are not added by default. To use the datapoints you will need to create datapoints called MemAdjustedUsed and MemAdjustedUsedPercent in the mem datasource on the device template.
CPU (in /Devices/Server/SSH/Linux)
HardDisk (in /Devices/Server/SSH/Linux)
There were significant changes between 2.4 and 2.6 in the I/O subsystem. As a result, some statistic information disappeared. The translation from a disk address relative to a partition to the disk address relative to the host disk happens much earlier. All merges and timings now happen at the disk level rather than at both the disk and partition level as in 2.4. There are only *four* fields available for partitions on 2.6 machines and in this case few datapoints will be missed.
IpService (in /Devices)
FileSystem (in /Devices/Server/SSH/Linux)
Filesystems will also show graphs from its related Logical Volume or Hard Disk.
ethernetCsmacd (in /Devices/Server/SSH/Linux)
SnapshotVolume (in /Devices/Server/SSH/Linux)
Snapshot Volumes will also show graphs from its related Volume Group and Hard Disk.
PhysicalVolume (in /Devices/Server/SSH/Linux)
Physical Volumes will also show graphs from its related Hard Disk.
VolumeGroup (in /Devices/Server/SSH/Linux)
Volume Groups will also show graphs from its related Physical Volumes.
LogicalVolume (in /Devices/Server/SSH/Linux)
Logical Volumes will also show graphs from its related Volume Group and Hard Disk.
ThinPool (in /Devices/Server/SSH/Linux)
Thin Pools will also show graphs from its related Volume Group and Hard Disk.
OSProcess (in /Devices/Server/SSH/Linux)
OSService-SYSTEMD (in /Devices/Server/SSH/Linux)
OSService-UPSTART (in /Devices/Server/SSH/Linux)
OSService-SYSTEMV (in /Devices/Server/SSH/Linux)
When combined with the Zenoss Service Dynamics product, this ZenPack adds built-in service impact capability for services running on Linux. 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
The following Linux distributions are officially supported. Other distributions may also be supported, especially derivatives of Debian and Red Hat Enterprise Linux.
View the discussion thread.
This ZenPack is developed and supported by Zenoss Inc. Contact Zenoss to request more information regarding this or any other ZenPacks. Click here to view all available Zenoss Open Source ZenPacks.