Monitoring Watcher
From ServersCheck Wiki
Overview
By default the ServersCheck performs basic fail-over capabilities for all versions: restart the monitoring_manager or monitoring_rule threads, if they die.
The ServersCheck Monitoring Software has an additional fail-over built-in system called the Monitoring Watcher. This additional application performs a more in depth fail-over: it will check if rules are still being executed and if not restart the service if needed (or perform a reboot). It will also track the individual thread's memory and restart a thread if it is being considered not OK. It can send alive messages to inform you that the monitoring software is still running. Finally it will inform you if the monitoring software is no longer working as expected.
This feature requires an Enterprise edition license key.
The Monitoring_Watcher.exe
This component is automatically launched by the Monitoring Service. Once launched, it runs outside the service so that it can influence the service if an error is detected.
If you run the Monitoring Service in interactive mode (Interact with desktop), then you will see a screen similar to following:
Every activity of the Monitoring Watcher is stored in a log file called: Watcher.log
The watcher.conf file
The watcher.conf file holds the configuration and is stored in the same directory as the monitoring_watcher. This file is not required. If it is not present, then ServersCheck will use its default values for the watcher.conf.
The default value being used is the timeout: what is the maximum interval during which no checks are performed before considering down. By default it is set to 900 seconds or 15 minutes.
Click here to download a sample watcher.conf file. The structure of the file is as follows: line 1 Timeout in seconds line 2 Email address to send email to if error is detected - uses settings of the service line 3 not used now - should be left blank line 4 Send an alive email every X hours. Only enter here the value for X line 5 Send an alive email to
