This is a collection of my custom NRPE compatible plugins.
This script queries the Snorby (https://github.com/Snorby/snorby) database for High severity events in a time interval. The time interval is defined by -i argument, the accepted arguments are integer values.
- Access to Snorby database
- Before executing the script you need to modify the database connection values defined inside the script
./check_snorby.sh -i <minutes>
OK - 0 High severity events in the defined interval
CRITICAL - 1 or more High severity events in the defined interval
UNKNOWN - something hasn't been set properly
$ ./check_snorby.sh -i 5
OK - 0 High severity events in the defined interval
$ ./check_snorby.sh -i 60000
CRITICAL - 14 High severity events in the defined interval
$ ./check_snorby.sh -i z
UNKNOWN - set the time interval to a integer value
- Copy the script to your nagios plugin directory (usually
/usr/lib64/nagios/plugins/) - Create the NRPE command, adding the following line to
/etc/nagios/nrpe.cfg(or where your nrpe definitions are stored)
command[check_snorby]=/usr/lib64/nagios/plugins/check_snorby.sh -i $ARG1$
- Create the service check adding the following definition in a .cfg file on
/etc/nagios/conf.d/(or where your nagios services definitions are stored)
define service{
use service-template
name Snorby High events
host_name hostname
service_description Snorby High events
check_command check_nrpe!check_snorby!30
}
This script checks the docker container internal CPU usage, it retrieves the values using docker stats.
- Docker 1.5.0 or higher
- The script requires sudo permissions due docker (this can be prevented if nrpe user is added to docker group)
sudo ./check_container_cpu.sh <container name> -w <warning threshold> -c <critical threshold>
OK - if the CPU usage is under the warning and critical thresholds
WARNING - if the CPU usage is equal or over the warning threshold and it is under the critical threshold
CRITICAL - if the CPU usage is equal or over the critical threshold
UNKNOWN - if the container does not exist
$ sudo ./check_container_cpu.sh container -w 80 -c 95
OK - CPU Usage = 7% | CPU Usage=7%;80;95;0;100
$ sudo ./check_container_cpu.sh container -w 80 -c 95
CRITICAL - CPU Usage = 97% | CPU Usage=97%;80;95;0;100
$ sudo ./check_container_cpu.sh notexist -w 80 -c 95
UNKNOWN - notexist does not exist.
- Copy the script to your nagios plugin directory (usually
/usr/lib64/nagios/plugins/) - This plugin needs sudo, so edit the sudoers config file as follow
$ sudo visudo
#Defaults requiretty
# Enable nagios to run restricted root checks
nrpe ALL=(ALL) NOPASSWD: /usr/lib64/nagios/plugins/check_container_cpu.sh
- Create the NRPE command, adding the following line to
/etc/nagios/nrpe.cfg(or where your nrpe definitions are stored)
command[check_container_cpu_usage]=sudo /usr/lib64/nagios/plugins/check_container_cpu.sh $ARG1$ -w $ARG2$ -c $ARG3$
- Create the service check adding the following definition in a .cfg file on
/etc/nagios/conf.d/(or where your nagios services definitions are stored)
define service{
use service-template
name Container CPU
host_name hostname
service_description Container CPU
check_command check_nrpe!check_container_cpu_usage!container!80!95
}
This script checks the docker container internal Memory usage, it retrieves the values using docker stats.
- Docker 1.5.0 or higher
- The script requires sudo permissions due docker (this can be prevented if nrpe user is added to docker group)
sudo ./check_container_memory.sh <container name> -w <warning threshold> -c <critical threshold>
OK - if the Memory usage is under the warning and critical thresholds
WARNING - if the Memory usage is equal or over the warning threshold and it is under the critical threshold
CRITICAL - if the Memory usage is equal or over the critical threshold
UNKNOWN - if the container does not exist
$ sudo ./check_container_memory.sh container -w 80 -c 95
OK - MEMORY Usage = 4.82% | Memory Usage=0.05%;80;95;0;100
$ sudo ./check_container_memory.sh container -w 80 -c 95
CRITICAL - MEMORY Usage = 96.79% | Memory Usage=96.79%;80;95;0;100
$ sudo ./check_container_memory.sh notexist -w 80 -c 95
UNKNOWN - notexist does not exist.
- Copy the script to your nagios plugin directory (usually
/usr/lib64/nagios/plugins/) - This plugin needs sudo, so edit the sudoers config file as follow
$ sudo visudo
#Defaults requiretty
# Enable nagios to run restricted root checks
nrpe ALL=(ALL) NOPASSWD: /usr/lib64/nagios/plugins/check_container_memory.sh
- Create the NRPE command, adding the following line to
/etc/nagios/nrpe.cfg(or where your nrpe definitions are stored)
command[check_container_memory_usage]=sudo /usr/lib64/nagios/plugins/check_container_memory.sh $ARG1$ -w $ARG2$ -c $ARG3$
- Create the service check adding the following definition in a .cfg file on
/etc/nagios/conf.d/(or where your nagios services definitions are stored)
define service{
use service-template
name Container Memory
host_name hostname
service_description Container Memory
check_command check_nrpe!check_container_memory_usage!container!80!95
}
This script checks the available memory on a Linux system.
- Nothing special, tools already bundled on every Linux system.
./check_avail_memory.sh -w <warning threshold> -c <critical threshold>
OK - if the available memory is above the warning and critical thresholds
WARNING - if the available memory is under the warning threshold and it is above the critical threshold
CRITICAL - if the available memory is under the critical threshold
$ ./check_avail_memory.sh -w 10 -c 5
OK - Available Memory = 89% | Available memory=89%;10;5;0;100
- Copy the script to your nagios plugin directory (usually
/usr/lib64/nagios/plugins/) - Create the NRPE command, adding the following line to
/etc/nagios/nrpe.cfg(or where your nrpe definitions are stored)
command[check_avail_memory]=/usr/lib64/nagios/plugins/check_avail_memory.sh -w $ARG1$ -c $ARG2$
- Create the service check adding the following definition in a .cfg file on
/etc/nagios/conf.d/(or where your nagios services definitions are stored)
define service{
use service-template
name Available Memory
host_name hostname
service_description Available Memory
check_command check_nrpe!check_avail_memory!10!5
}
This script checks the diskspace available to docker daemon.
- docker 1.12 or lower. (This script doesn't work with docker 1.13 due different
docker infocommand output). - The script requires sudo permissions due docker (this can be prevented if nrpe user is added to docker group)
sudo ./check_docker_dataspace.sh -w <warning threshold> -c <critical threshold>
OK - if the available disk space is under the warning and critical thresholds
WARNING - if the available disk space is equal or over the warning threshold and it is under the critical threshold
CRITICAL - if the available disk space is equal or over the critical threshold
UNKNOWN - if the docker daemon isn't running
$ ./check_docker_dataspace.sh -w 20 -c 15
OK - Available Data Space = 96% | Available space=96%;20;15;0;100
- Copy the script to your nagios plugin directory (usually
/usr/lib64/nagios/plugins/) - This plugin needs sudo, so edit the sudoers config file as follow
$ sudo visudo
#Defaults requiretty
# Enable nagios to run restricted root checks
nrpe ALL=(ALL) NOPASSWD: /usr/lib64/nagios/plugins/check_docker_dataspace.sh
- Create the NRPE command, adding the following line to
/etc/nagios/nrpe.cfg(or where your nrpe definitions are stored)
command[check_docker_dataspace]=sudo /usr/lib64/nagios/plugins/check_docker_dataspace.sh -w $ARG1$ -c $ARG2$
- Create the service check adding the following definition in a .cfg file on
/etc/nagios/conf.d/(or where your nagios services definitions are stored)
define service{
use service-template
name Docker data space
host_name hostname
service_description Docker data space
check_command check_nrpe!check_docker_dataspace!10!5
}
GNU GENERAL PUBLIC LICENSE Version 3