The application check_site_simple is a program to check the availability and integrity of html based websites. It works as a monitoring-plugin for Nagios-compatible system-monitoring frameworks.
To successfully install, configure and run check_site_simple as monitoring-plugin you will need:
CNR-*_check_site.dat) which you can download from the distributors portal (see Contact for how to buy ).check_site_simple is a ready-to-use compiled binary without any
dependency. It can be started from the commandline as
./check_site_simple after download. It is aimed to be run either
as active check (check_site_simple --url=https://www.example.com)
or
via cron on a regular base feeding it’s output to the monitoring-daemon trough a pipe. In other words: check_site_simple can also be used for passive-checks.
We recommend the configuration as active check for new users.
Copy both the binary and the license file from the tar-achive you received to the monitoring server. Using their default locations will shorten the following configuration process a bit.
The detailed steps to install check_site_simple on the monitoring server are:
Copy the binary check_site_simple to its default directory. (Create that directory if it does not already exist.)
mkdir -p /usr/local/monitoring-plugins.pro/check-site/var
tar xvzf check-site-1.0.0.tar.gz --directory=/usr/local/monitoring-plugins.pro/check-site/
Any other directory beside the default is fine as well. But in that case you need to adapt the example configuration file if you use it.
Copy the license-file to its default location /usr/local/monitoring-plugins.pro/check-site/etc. If this path does not exist, create it.
mkdir -p /usr/local/monitoring-plugins.pro/check-site
mv CNR-01144-X1B0D2_check_site.dat
/usr/local/monitoring-plugins.pro/check-site/etc
Any other directory for the license-file is fine as well. But than you need to tell the plugins about its location with the --license-dir parameter.
Check if it works. E.g. ./check_site_simple --version should write the programs version string to the console.
That’s it! You can now continue with the configuration.