Documentation

Alerting

LPAR2RRD has build-in alerting feature.
You can define alarms based on performance data for CPU pool, LPAR, VM in your environment.

Metrics

objectmetricvaluedata sourceNote
ALL servers Paging MB/sec OS agent
server CPU CPU core or % HMCIBM Power only
CPU POOL CPU CPU core or % HMCIBM Power only
LPAR CPU CPU core or % HMCIBM Power only
LPAR / VM CPU OS % OS agent
LPAR / VM Memory used % OS agent
LPAR / VM Paging MB/sec OS agent
LPAR / VM Paging allocation % OS agent
LPAR / VM LAN MB/sec OS agent
LPAR / VM SAN MB/sec OS agent
LPAR / VM SAN IOPS OS agent
LPAR / VM SAN response time mili seconds OS agent
LPAR / VM Filesystem usage % OS agent

Alerting possibilities

  • Emailing. You can place direct email address on each directive, use email groups or default email address.
  • Nagios support. You can configure Nagios to pick up alarms from LPAR2RRD via standard NRPE module.
    LPAR2RRD Nagios plug-in installation
  • External alerting via external shell script. Each alert can invoke defined script with given parameters. You can use it for your integration needs.
  • SNMP trap: follow this to configure it
  • Alert plug-ins to other monitoring tools can be developed on demand especially for customers under support contract

Configuration

Configuration is managed through the UI ➡ Settings ➡ Alerting

To allow HMC data based alerting place this job into lpar2rrd's crontab:
Note: If you use HMC REST API then this is not necessary!
0,10,20,30,40,50 * * * * /home/lpar2rrd/lpar2rrd/load_alert.sh > /home/lpar2rrd/lpar2rrd/load_alert.out 2>&1

Email setup

Use your company's default email setup on the operating system you run LPAR2RRD.
There is no any specific setup in the tool, it uses setting on the operating system.
In case of problems
  • Try send out a testing email from cmd line:
    $ echo "test message"| mailx -s test your_email@company.com
    
  • Check success in mail log /var/log/maillog (Linux), /var/log/mail (AIX)
Email setup on the Virtual Appliance