
Resource monitoring can be viewed as two separate tasks: the testing of a condition, and triggering some sort of action upon failure. mon was designed to keep the testing and action-taking tasks separate, as stand-alone programs. mon is implemented as a scheduler which executes the the monitors (which test a condition), and calls the appropriate alerts if the monitor fails.
Monitors and alerts are not a part of mon, even though the distribution comes with a handful of them to get you started. This means that if a new service needs monitoring, or if a new alert is required, the mon server does not need to be changed. This makes mon easily extensible.
mon currently monitors over two hundred hosts at our site, using the monitor scripts which are supplied with the distribution.
Jim Trocki
and generated with m4