About
The check plugin check_autoremove monitors whether any software packages were just dependencies of others and may be removed.
Usage
The plug-and-play Linux binaries take the following CLI arguments and no environment variables:
$ ./check_autoremove [-warn THRESHOLD] [-crit THRESHOLD]THRESHOLD specifies an alert threshold range
conforming to the Nagio$ check plugin API,
e.g. -warn @~:42 warns if there are <= 42 unneeded dependencies.
Legal info
To print the legal info, execute the plugin in a terminal:
$ ./check_autoremoveIn this case the program will always terminate with exit status 3 ("unknown") without actually checking anything.
Testing
If you want to actually execute a check inside a terminal, you have to connect the standard output of the plugin to anything other than a terminal – e.g. the standard input of another process:
$ ./check_autoremove |catIn this case the exit code is likely to be the cat's one. This can be worked around like this:
bash $ set -o pipefail
bash $ ./check_autoremove |catActual monitoring
Just integrate the plugin into the monitoring tool of your choice like any other check plugin. (Consult that tool's manual on how to do that.) It should work with any monitoring tool supporting the Nagio$ check plugin API.
Limitations:
- check_autoremove must be run on the host to be checked – either with an agent of your monitoring tool or by SSH. Otherwise it will check the host your monitoring tool runs on.
- The check_autoremove binary must be owned by root
and the setuid bit must be set, i.e.:
chown root .../check_autoremove; chmod u+s .../check_autoremove
Icinga 2
This repository ships the check command definition as well as a service template and host example for Icinga 2.
The service definition will work in both correctly set up Icinga 2 clusters and Icinga 2 instances not being part of any cluster as long as the hosts are named after the endpoints.
