ZenPack:Linux Monitor

From Zenoss Wiki
Revision as of 22:28, 24 February 2014 by Bbruggeman (Talk | contribs)$7

Jump to: navigation, search

Note: This is a Core ZenPack which can be found in the Core Zenoss RPM, and is fully documented in the Zenoss Extended Monitoring Guide. If you did not install this pack when you installed Zenoss Core, it can be found in $ZENHOME/packs.

Organization
Zenoss, Inc.
ZenPack name
ZenPacks.zenoss.LinuxMonitor
Link to more docs
View Documentation




Linux Monitor ZenPack

This ZenPack monitors Linux systems via ssh.

Warning

The ZenPack Catalog has moved to its new home at https://www.zenoss.com/product/zenpacks as of January 17, 2017. The following information may be out of date, and this page will eventually be removed.

Support

This ZenPack is part of Zenoss Core. Open Source users receive community support for this ZenPack via our online forums. Enterprise support for this ZenPack is provided to Zenoss customers with an active subscription.

Background

The ZenPacks.zenoss.LinuxMonitor ZenPack demonstrates how to develop new plugins that collect performance data using Secure Shell.


This ZenPack demonstrates the Secure Shell (SSH) features, and enables modeling and monitoring several types of device components for 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.


Prerequisites

Prerequisite Restriction
Product Zenoss platform 4.x, Zenoss 2.4 or higher
Required ZenPacks ZenPacks.zenoss.LinuxMonitor


Set Linux Server Monitoring Credentials

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.
    Linux Configuration Properties
    Name Description
    zCommandUsername Linux user with privileges to gather performance information.
    zCommandPassword Password for the Linux user.



Add a Linux Server

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.


Daemons

Type Name
Modeler zenmodeler
Performance Collector zencommand

Installation

Normal Installation (packaged egg)

  1. Download the appropriate egg file for the version of Zenoss you are running.
  2. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  3. Install the ZenPack:
    $ zenpack --install ZenPacks.zenoss.LinuxMonitor-*.egg
  4. Restart these services:
    $ zenoss restart

Developer Mode Installation

In order to do a development mode installation you will want to clone the existing git repository, and then use the --link flag with the zenpack command:

  1. Ensure you are logged in as the zenoss user:
    $ sudo su - zenoss
  2. Start by cloning the upstream repository:
    $ git clone git://github.com/path/to/repo
  3. Next, perform the installation:
    $ zenpack --link --install ZenPacks.zenoss.LinuxMonitor
  4. Finally, restart these serivices:
    $ zenoss restart

Discuss

Purplemarker.png New: Don't forget to add yourself to the Zenoss User Map!

blog comments powered by Disqus