/build/static/layout/Breadcrumb_cap_w.png

K1000 Non-Windows Monitoring Log Enablement Package (LEP) Library



Overview

The 6.3 release of the K1000 appliance adds a log monitoring feature for server operating systems. In addition, a set of "Log Enablement Package" have been created to monitor system performance and write alerts to log files when a defined threshold has been exceeded. This page provides an overview of the Log Enablement Package created for non-Windows operating systems. Each Log Enablement Package is a Perl script designed to run periodically using the built-in OS scheduler (cron, fcron, etc). When executed, the Perl scripts run a series of commands to determine the utilization of CPU, memory and local volumes. An alert is written to the system log (syslog) file if the utilization exceeds the defined threshold.


Log Enablement Package (LEP)

Operating System

OS Version

Log Enablement Package

Mac OS X

10.6.x - 10.9.x

K1000MonitoringMacOSX_LEP

Linux/FreeBSD

Newest 4 versions of each OS

K1000MonitoringLinux_LEP

HP-UX

11.2x and 11.3x

K1000MonitoringHP-UX_LEP

IBM AIX

5.x - 7.x

K1000MonitoringIbmAIX_LEP

Solaris

Intel/SPARC, 10.x - 11.x

K1000MonitoringSolaris_LEP


Metrics

Metric

Default Threshold

CPU usage

85%

Physical memory usage

85%

Local logical volume usage

85%


Instructions

The following instructions explain how to set up a Red Hat Enterprise Linux system with the K1000 Linux ITNinja Log Enablement Package. The procedure is nearly the same for each non-Windows operating system.

  1. Add a new agent or agentless device to inventory using the K1000 administrative interface and ensure an inventory runs successfully.

  2. Copy the Perl script K1000MonitoringLinuxPlugin.pl to the target device.

  3. Open K1000MonitoringLinuxPlugin.pl in a text editor.

  4. The configuration settings for the script are at the top. The default thresholds and alert prefix can be changed if desired. Note the alert prefix because this will be used in a later step.

  5. Execute the script using Perl to verify it runs without errors:

    perl K1000MonitoringLinuxPlugin.pl

  6. Schedule the script to run periodically using the built-in OS scheduler (i.e, cron, fcron, etc). A 10 minute interval is good starting point.

  7. On the K1000, click Inventory > Devices. Click on the device to view its details.

  8. Scroll down to the Activities section and click Monitoring. Click Enable Monitoring.

  9. The next step is to set up a monitoring profile to pick up alerts on the target device. Click Monitoring > Profiles.

  10. At this point a new profile can be created or an existing one can be modified. In this example a new profile will be created.

  11. Click Choose Action > New. Provide a name for this monitoring profile (i.e., K1000 Linux ITNinja LEP). Additionally, a description may be specified but it is not required.

  12. Specify the full path and name of the system log (syslog). Use the following value for Red Hat Enterprise Linux:

    /var/log/messages

  13. Leave the Log Date Format empty for syslog logs.

  14. Click the plus sign under Criteria.

  15. Set the alert level to the desired level.

  16. Set the search text to the alert prefix specified in the Perl script K1000MonitoringLinuxPlugin.pl. The default alert prefix is:

    K1000 monitor alert:

  17. Click Save next to the criteria.

  18. Click Save at the bottom of the page.

  19. Click Monitoring > Devices.

  20. Click the target device.

  21. Add the profile created in the previous step under "Profiles". This can be done by clicking in the space under "Profiles:" and selecting the newly created profile.

  22. Click Save at the bottom of the page.




Comments

This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ