Monitoring Progress Databases

[Jim Avery]

On 23/07/07, Mies, Christian <c.mies at itnovum.de> wrote:
>
> Christian Mies schrieb am 23.07.2007 11:26
>
> Hi  List,
>
> has anybody  experience in Monitoring Progress Databases?
> If I see it  correctly Progress DBs are only Files, that have a fix Filesize and some  Logfiles. Is it right?
> Or is there a ODBC  Driver for Connecting through a Progress DB?
>
> Any  Hints?

The database log file is pretty easy to monitor.  The trick is to
filter out anything you're not interested in.  I rewrote the standard
check_logs plugin slightly to allow the "-v" option in egrep.  I can
then run the plugin something like so:

/usr/local/nagios/libexec/check_logv -F /user/dbasedir/dbase.lg -O
/tmp/dbase.lg.old -v -q \
 ': \(-----\) Database dbase Options:|: \(-----\) Event Logger error
997:|: \(-----\) Registry error 5:|: \(452\) |: \(453\) |: \(562\) |:
\(739\) |: \(742\) |: \(794\) |: \(2252\) |: \(2253\) |: \(2518\) |:
\(3777\) |: \(3778\) |: \(3789\) |: \(5512\) |: \(5644\) |: \(5645\)
|: \(7129\) |: \(8846\) |: \(8864\) |: \(8873) |: \(12699\) |:
\(13199\) |\^\$|      Mon |      Tue |      Wed |      Thu |      Fri
|      Sat |      Sun '

I only implemented this recently so it needs a little polishing still.
 I'd also rather get egrep to take its arguments line by line from a
file, so I'll probably rewrite it one day when I get around to it.
The "\^\$" thing I put there to make it ignore blank lines, but that
doesn't seem to work quite right yet.  The days of the week are there
because Progress writes the date to the log file every day and I want
to ignore that.

If you read some of the documentation, it might tell you that an "I"
in the log file means "Informational" implying that there might be a
"W" for warnding "C" for critical and so on.  Don't believe it!  In a
test database, I even deleted one of the extent files and the message
in the log file still only had "I" in it.

One really important thing to monitor in Progress is the size of the
BI storage area.  You can monitor the size of the extent file using
standard plugins and make it alert when it gets to a size somewhat
lower than whatever you've set the BI threshold parameter to in
Progress.  Other storage areas you can monitor (for size anyway) in a
similar fashion.  We went one step further and wrote a little Progress
program to dump some of the virtual system tables to an ascii file.  I
use a simple script to read the file and return results back to Nagios
using nsca.

I monitor the number of licenses used with a simple script which reads
the dbname.lic file.

I've only been monitoring Progress OpenEdge 10 for a few weeks myself,
so I haven't gotten around to publishing any of my plugins or scripts
yet.  Before doing so, I need to tidy them up a bit, as the way I do
things using nsca is a bit non-standard but works for me.  If you'd
like them in their rough form anyway, give me a shout and I'll be
happy to email them to you.

hth,

Jim

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null