Home Directory Plugins Databases DB2 Monitor DB2 with Nagios

Search Exchange

Search All Sites

Nagios Live Webinars

Let our experts show you how Nagios can help your organization.

Contact Us

Phone: 1-888-NAGIOS-1
Email: sales@nagios.com


Remember Me
Don't miss your chance to attend the 2014 Nagios World conference!

Don't miss your chance to attend the 2014 Nagios World Conference, Oct 13-16th. Informative Sessions, Networking, Food and Cocktails! Visit go.nagios.com/conference/ for more information or to register.

Monitor DB2 with Nagios

Bookmark and Share

Current Version
Last Release Date
Compatible With
  • Nagios 3.x
db2diag.pngGraph from check_db2diag
Set of Bash scripts to monitor DB2 with Nagios.

They also retrieve performance data in order to create graphs.
This set of scripts is in continuos development, thus new scripts are being developed and other are already planned. If you want to share your own modification, I will merge them in my trunk.

For the moment, you can monitor:

* Quantity of connexions, filtered by many criteria (machines, users) and showing their status.
* Checks if a connection to the database can be established.
* Checks the database size. Based on the Storage management utility - http://publib.boulder.ibm.com/infocenter/db2luw/v10r1/topic/com.ibm.db2.luw.sql.rtn.doc/doc/r0023696.html
* Checks the HADR status, by analyzing peer status and calcutating the difference between primary et standby (logs et pages)
* Checks if the instance is active.
* Keeps a history of last backups (full, delta, incremental) and could throw an alert if the backup is too old.
* Checks the locks looking for long term lock waints, returning with process is holding the locks.
* Checks the log consumption per day. Allows you indentify the most expensive transaction measured by logs produced.
* Log usage, that allows you identify how many primary and secondary logs are being used.
* Tablespace: Use and state (normal, backup, etc.)
* Utilities: Allows you to identify which utilities could impact the normal db usage.

This set of script, as many other tools to monitor DB2, and in general form databases, has the problem that the connection has to be reestablished each time a request to the database is done. I mean, if you configure all scripts (and one tablespace), and Nagios active all of them in a 10 minutes lapse, it mean, that you can establish around 20 connections. This could create an overhead, but if you add the server access, this could imply NRPE or ssh access.
This problem is well-known and I am currently working in a new version, where the architecture will be completly different.