Alerting
LPAR2RRD has build-in alerting feature.
It works for IBM Power Systems, Oracle Database and Linuxes which have installed
OS agent only.
You can define alarms based on performance data for CPU pool, LPAR, VM in your environment.
Metrics: IBM Power System
object | metric | value | data source | Note |
ALL servers | Paging | MB/sec | OS agent | |
server | CPU | CPU core or % | HMC | IBM Power only |
CPU POOL | CPU | CPU core or % | HMC | IBM Power only |
LPAR | CPU | CPU core or % | HMC | IBM Power only |
LPAR | CPU OS | % | OS agent | |
LPAR | Memory used | % | OS agent | |
LPAR | Paging | MB/sec | OS agent | |
LPAR | Paging allocation | % | OS agent | |
LPAR | LAN | MB/sec | OS agent | |
LPAR | SAN | MB/sec | OS agent | |
LPAR | SAN | IOPS | OS agent | |
LPAR | SAN response time | mili seconds | OS agent | |
LPAR | Filesystem usage | % | OS agent | |
Metrics: Linux with the OS agent
object | metric | value | data source | Note |
VM | CPU OS | % | OS agent | |
VM | Memory used | % | OS agent | |
VM | Paging | MB/sec | OS agent | |
VM | Paging allocation | % | OS agent | |
VM | LAN | MB/sec | OS agent | |
VM | SAN | MB/sec | OS agent | |
VM | SAN | IOPS | OS agent | |
VM | SAN response time | mili seconds | OS agent | |
VM | Filesystem usage | % | OS agent | |
Metrics: Oracle Database
object | metric | value |
Database | Current logons count | number |
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
IBM Power Systems
To allow HMC data based alerting place (CPU core for LPAR/POOL/POOL Total) this job into lpar2rrd's crontab:
This is valid only if you use HMC CLI (ssh) access, HMC REST API does not need it.
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
Email setup on the Virtual Appliance