pkg-monitoring-plugins/plugins-scripts/check_log.sh

212 lines
5.7 KiB
Bash
Raw Normal View History

2013-11-26 22:53:19 +00:00
#!/bin/sh
#
2014-07-11 19:01:00 +00:00
# Log file pattern detector plugin for monitoring
2013-11-26 22:53:19 +00:00
# Written by Ethan Galstad (nagios@nagios.org)
# Last Modified: 07-31-1999
#
# Usage: ./check_log <log_file> <old_log_file> <pattern>
#
# Description:
#
# This plugin will scan a log file (specified by the <log_file> option)
# for a specific pattern (specified by the <pattern> option). Successive
# calls to the plugin script will only report *new* pattern matches in the
# log file, since an copy of the log file from the previous run is saved
# to <old_log_file>.
#
# Output:
#
# On the first run of the plugin, it will return an OK state with a message
# of "Log check data initialized". On successive runs, it will return an OK
# state if *no* pattern matches have been found in the *difference* between the
# log file and the older copy of the log file. If the plugin detects any
# pattern matches in the log diff, it will return a CRITICAL state and print
# out a message is the following format: "(x) last_match", where "x" is the
# total number of pattern matches found in the file and "last_match" is the
# last entry in the log file which matches the pattern.
#
# Notes:
#
# If you use this plugin make sure to keep the following in mind:
#
2014-07-11 19:01:00 +00:00
# 1. The "max_attempts" value for the service should be 1, as this will
# prevent the monitoring system from retrying the service check (the
2013-11-26 22:53:19 +00:00
# next time the check is run it will not produce the same results).
#
2014-07-11 19:01:00 +00:00
# 2. The "notify_recovery" value for the service should be 0, so that the
# monitoring system does not notify you of "recoveries" for the check.
# Since pattern matches in the log file will only be reported once and
# not the next time, there will always be "recoveries" for the service,
# even though recoveries really don't apply to this type of check.
2013-11-26 22:53:19 +00:00
#
# 3. You *must* supply a different <old_file_log> for each service that
# you define to use this plugin script - even if the different services
# check the same <log_file> for pattern matches. This is necessary
# because of the way the script operates.
#
# Examples:
#
# Check for login failures in the syslog...
#
# check_log /var/log/messages ./check_log.badlogins.old "LOGIN FAILURE"
#
# Check for port scan alerts generated by Psionic's PortSentry software...
#
# check_log /var/log/message ./check_log.portscan.old "attackalert"
#
# Paths to commands used in this script. These
# may have to be modified to match your system setup.
PROGNAME=`/bin/basename $0`
PROGPATH=`echo $0 | sed -e 's,[\\/][^\\/][^\\/]*$,,'`
REVISION="@NP_VERSION@"
2014-07-11 19:01:00 +00:00
PATH="@TRUSTED_PATH@"
export PATH
2013-11-26 22:53:19 +00:00
. $PROGPATH/utils.sh
print_usage() {
echo "Usage: $PROGNAME -F logfile -O oldlog -q query"
echo "Usage: $PROGNAME --help"
echo "Usage: $PROGNAME --version"
}
print_help() {
print_revision $PROGNAME $REVISION
echo ""
print_usage
echo ""
2014-07-11 19:01:00 +00:00
echo "Log file pattern detector plugin for monitoring"
2013-11-26 22:53:19 +00:00
echo ""
support
}
# Make sure the correct number of command line
# arguments have been supplied
if [ $# -lt 1 ]; then
print_usage
exit $STATE_UNKNOWN
fi
# Grab the command line arguments
#logfile=$1
#oldlog=$2
#query=$3
exitstatus=$STATE_WARNING #default
while test -n "$1"; do
case "$1" in
--help)
print_help
exit $STATE_OK
;;
-h)
print_help
exit $STATE_OK
;;
--version)
2013-11-26 22:54:42 +00:00
print_revision $PROGNAME $REVISION
2013-11-26 22:53:19 +00:00
exit $STATE_OK
;;
-V)
2013-11-26 22:54:42 +00:00
print_revision $PROGNAME $REVISION
2013-11-26 22:53:19 +00:00
exit $STATE_OK
;;
--filename)
logfile=$2
shift
;;
-F)
logfile=$2
shift
;;
--oldlog)
oldlog=$2
shift
;;
-O)
oldlog=$2
shift
;;
--query)
query=$2
shift
;;
-q)
query=$2
shift
;;
-x)
exitstatus=$2
shift
;;
--exitstatus)
exitstatus=$2
shift
;;
*)
echo "Unknown argument: $1"
print_usage
exit $STATE_UNKNOWN
;;
esac
shift
done
# If the source log file doesn't exist, exit
if [ ! -e $logfile ]; then
2014-07-11 19:01:00 +00:00
echo "Log check error: Log file $logfile does not exist!"
2013-11-26 22:53:19 +00:00
exit $STATE_UNKNOWN
elif [ ! -r $logfile ] ; then
2014-07-11 19:01:00 +00:00
echo "Log check error: Log file $logfile is not readable!"
2013-11-26 22:53:19 +00:00
exit $STATE_UNKNOWN
fi
# If the old log file doesn't exist, this must be the first time
# we're running this test, so copy the original log file over to
# the old diff file and exit
if [ ! -e $oldlog ]; then
2014-07-11 19:01:00 +00:00
cat $logfile > $oldlog
echo "Log check data initialized..."
2013-11-26 22:53:19 +00:00
exit $STATE_OK
fi
# The old log file exists, so compare it to the original log now
# The temporary file that the script should use while
# processing the log file.
if [ -x /bin/mktemp ]; then
tempdiff=`/bin/mktemp /tmp/check_log.XXXXXXXXXX`
else
tempdiff=`/bin/date '+%H%M%S'`
tempdiff="/tmp/check_log.${tempdiff}"
2014-07-11 19:01:00 +00:00
touch $tempdiff
chmod 600 $tempdiff
2013-11-26 22:53:19 +00:00
fi
2014-07-11 19:01:00 +00:00
diff $logfile $oldlog | grep -v "^>" > $tempdiff
2013-11-26 22:53:19 +00:00
# Count the number of matching log entries we have
2014-07-11 19:01:00 +00:00
count=`grep -c "$query" $tempdiff`
2013-11-26 22:53:19 +00:00
# Get the last matching entry in the diff file
2014-07-11 19:01:00 +00:00
lastentry=`grep "$query" $tempdiff | tail -1`
2013-11-26 22:53:19 +00:00
2014-07-11 19:01:00 +00:00
rm -f $tempdiff
cat $logfile > $oldlog
2013-11-26 22:53:19 +00:00
if [ "$count" = "0" ]; then # no matches, exit with no error
2014-07-11 19:01:00 +00:00
echo "Log check ok - 0 pattern matches found"
2013-11-26 22:53:19 +00:00
exitstatus=$STATE_OK
else # Print total matche count and the last entry we found
2014-07-11 19:01:00 +00:00
echo "($count) $lastentry"
2013-11-26 22:53:19 +00:00
exitstatus=$STATE_CRITICAL
fi
exit $exitstatus