This ZenPack provided monitoring support for Linux, leveraging OpenSSH for data access. In addition to system health, disks, LVM, services, and processes are monitored.

• Monitors multiple Linux flavors and versions
• OpenStack LVM volume integration
• Monitors LVM Physical Volumes, Volume Groups, and Logical Volumes
• Block Device monitoring
• Service Monitoring via Sysvinit, Systemd, Upstart
• Root Cause Analysis with Impact Support
• Dynamic View support

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.

Hard Disks

Attributes: Name, Size, LVM PV

Processors

Attributes: Socket, Manufacturer, Model, Speed, Ext Speed, L1, L2, Voltage

IP Services

Attributes: Name, Protocol, Port, IPs, Description

File Systems

Attributes: Mount Point, Storage Device, Total Bytes, Used Bytes, Free Bytes, % Util

Interfaces

Attributes: IP Interface, IP Addresses, Description, MAC Address, Operational Status, Admin Status

Network Routes

Attributes: Destination, Next Hop, Interface, Protocol, Type

Snapshot Volumes

Attributes: Name, Volume Group, Logical Volume, Size, Block Device, File System, Active

Relations: Logical Volumes

Physical Volumes

Attributes: Name, Format, Size, Free, % Util, Block Device, Volume Group

Relations: Volume Groups

Volume Groups

Attributes: Name, Size, Free, % Util, Snapshot Volumes, Logical Volumes, Physical Volumes

Logical Volumes

Attributes: Name, Volume Group, Size, Block Device, File System, Active, Snapshot Volumes

Relations: Volume Groups

OS Processes

Attributes: Process Class, Process Set, Restart Alert?, Fail Severity

OS Services

Attributes: Name, Loaded Status, Active Status, Main PID, Processes, Description

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.

1. Select Infrastructure from the navigation bar.
2. Click the device name in the device list. The device overview page appears.
3. Select Configuration Properties from the left panel.
4. Verify the credentials for the service account. 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 linux 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.

   Using a Root User

   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.
   1. Install the sudo package on your server.
   2. Allow root user to execute commands via ssh without a TTY.
      1. Edit the /etc/sudoers file.
      2. Find the line containing root ALL=(ALL) ALL.
      3. Add this line underneath it:

         Defaults:root !requiretty

      4. Save the changes and exit.

   Using a Non-Root User

   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, most of these commands are only allowed to be run by the root user. The output of systemctl, initctl 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.
   1. Install the sudo package on your server
   2. 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::

        Defaults:zenmonitor        !requiretty
        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 status *, /sbin/initctl list, /sbin/service --status-all, \
              /usr/sbin/dmidecode
        zenmonitor ALL=(ALL) NOPASSWD: ZENOSS_LVM_CMDS, ZENOSS_SVC_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. 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. Linux Configuration Properties

   Name	Description
   zCommandUsername	Linux user with privileges to gather performance information.
   zCommandPassword	Password for the Linux user.

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.

1. Select Infrastructure from the navigation bar.
2. Select Add a Single Device from the Add Device list of options. The Add a Single Device dialog appears.
3. Enter the following information in the dialog: Adding Linux Device Details

   Name	Description
   Name or IP	Linux host to model.
   Device Class	/Server/SSH/Linux
   Model Device	Select this option unless adding a device with a user name and password different than found in the device class. If you do not select this option, then you must add the credentials (see) and then manually model the device.

4. Click Add.

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...

<syntaxhighlight lang="text"> /Devices/Server/Linux LinuxDevice zCommandUsername="user", zCommandPassword="password" </syntaxhighlight>

You can then load the Linux servers into Zenoss Core or Resource Manager as devices with the following command.

<syntaxhighlight lang="bash"></syntaxhighlight> zenbatchload <filename> &lt;/syntaxhighlight&gt;</filename>

Installing this ZenPack will add the following items to your Zenoss system.

Device Classes

• /Server/SSH/Linux

Modeler Plugins

• zenoss.cmd.uname
• zenoss.cmd.linux.df
• zenoss.cmd.linux.alt_kernel_name
• zenoss.cmd.linux.cpuinfo
• zenoss.cmd.linux.interfaces
• zenoss.cmd.linux.lvm
• zenoss.cmd.linux.memory
• zenoss.cmd.linux.netstat_an
• zenoss.cmd.linux.netstat_rn
• zenoss.cmd.linux.process
• zenoss.cmd.linux.rpm
• zenoss.cmd.linux.sudo_dmidecode
• zenoss.cmd.linux.os_release
• zenoss.cmd.linux.os_service

Monitoring Templates

• Device (in /Devices/Server/SSH/Linux)
• HardDisk (in /Devices/Server/SSH/Linux)
• IpService (in /Devices)
• FileSystem (in /Devices/Server/SSH/Linux)
• ethernetCsmacd (in /Devices/Server/SSH/Linux)
• SnapshotVolume (in /Devices/Server/SSH/Linux)
• PhysicalVolume (in /Devices/Server/SSH/Linux)
• VolumeGroup (in /Devices/Server/SSH/Linux)
• LogicalVolume (in /Devices/Server/SSH/Linux)
• OSProcess (in /Devices/Server/SSH/Linux)

Device (in /Devices/Server/SSH/Linux)

• Data Points
  • ssCpuIdlePerCpu
  • ssCpuUserPerCpu
  • ssCpuSystemPerCpu
  • ssCpuWaitPerCpu
  • sysUpTime
  • laLoadInt15
  • laLoadInt5
  • laLoadInt1
  • Buffers
  • Cached
  • MemFree
  • MemTotal
  • SwapFree
  • SwapTotal
  • ssIORawReceived
  • ssIORawSent
• Thresholds
  • None
• Graphs
  • CPU Utilization
  • Load Average
  • Memory Utilization
  • Memory Usage
  • IO Throughput

HardDisk (in /Devices/Server/SSH/Linux)

• Data Points
  • readsCompleted
  • readsMerged
  • sectorsRead
  • msReading
  • writesCompleted
  • writesMerged
  • sectorsWritten
  • msWriting
  • ioInProgress
  • msDoingIO
  • msDoingIOWeighted
• Thresholds
  • None
• Graphs
  • Operation Throughtput
  • Merge Rate
  • Sector Throughtput
  • IO Operation in Progress
  • IO Utilization
  • Weighted IO Utilization

IpService (in /Devices)

• Data Points
  • None
• Thresholds
  • None
• Graphs
  • None

FileSystem (in /Devices/Server/SSH/Linux)

• Data Points
  • usedBlocks
  • percentInodesUsed
  • totalInodes
  • usedInodes
  • availableInodes
• Thresholds
  • 90 percent used
• Graphs
  • Utilization
  • Usage
  • Inode Utilization
  • Inode Usage

ethernetCsmacd (in /Devices/Server/SSH/Linux)

• Data Points
  • ifInOctets
  • ifOutOctets
  • ifInPackets
  • ifOutPackets
  • ifInErrors
  • ifInDropped
  • ifInOverruns
  • ifOutErrors
  • ifOutCarrier
  • ifOutCollisions
  • ifOutDropped
• Thresholds
  • 75 percent utilization
• Graphs
  • Data Throughput
  • Packet Throughput
  • Error Rate

SnaphotVolume (in /Devices/Server/SSH/Linux)

• Data Points
  • state
  • health
• Thresholds
  • None
• Graphs
  • None

PhysicalVolume (in /Devices/Server/SSH/Linux)

• Data Points
  • size
  • free
  • allocatable
  • exported
  • missing
• Thresholds
  • unallocatable
  • exported
  • missing
• Graphs
  • Utilization

VolumeGroup (in /Devices/Server/SSH/Linux)

• Data Points
  • size
  • free
  • partial
• Thresholds
  • partial
• Graphs
  • Utilization

LogicalVolume (in /Devices/Server/SSH/Linux)

• Data Points
  • state
  • health
• Thresholds
  • None
• Graphs
  • None

OSProcess (in /Devices/Server/SSH/Linux)

• Data Points
  • count
  • cpu
  • mem
• Thresholds
  • count
• Graphs
  • Process Count
  • CPU Utilization
  • Memory Usage

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

• HardDisk, IpInterface, IpService, OSProcess, CPU, OSService are impacted by LinuxDevice;
• PhysicalVolume is impacted by HardDisk;
• VolumeGroup is impacted by PhysicalVolume;
• LogicalVolume is impacted by VolumeGroup or HardDisk;
• SnapshotVolume is impacted by LogicalVolume or HardDisk;
• FileSystem is impacted by SnapshotVolume or LogicalVolume or HardDisk or LinuxDevice

The following flavors of Linux are supported

2.1.0

• Prevent threshold violations on interfaces with unknown speed.
• Add common datapoint aliases. (ZEN-24619)

2.0.6

• Fix "string index out of range" error when modeling older LVM versions (ZEN-25792)

2.0.4

• Fix "unimplemented" SSH error on 4.2.5 SP709. (ZEN-23392)

2.0.3

• Fix migration of Linux devices to new type. (ZEN-24293)

2.0.2

• Added property to ignore unmounted hard disks
• Improve 1.x to 2.x migration time. (ZEN-24024)

2.0.1

• Fix invalid event class in filesystem threshold

2.0.0

• Added support for LVM Physical Volumes, Volume Groups, and Logical Volumes
• Added support for OpenStack-LVM Integration
• Added disk (block device) monitoring.
• Added service monitoring (sysvinit, systemd, upstart).
• Combined EnterpriseLinux and LinuxMonitor capabilities.
• Enhanced Impact Support
• Added Dynamic View Support
• Completely replaces EnterpriseLinux ZenPack
• Many other smaller improvements.

• The endpoint device type was changed to LinuxDevice
• Impact Changes: GUID's are changed:
  • Since Linux device type was changed (see above), the GUID's of the Linux objects are also changed at upgrade. This implies that the original impact graph will lose the associated Linux devices at upgrade. Re-add the Linux devices to the impact diagram to restore these objects.