mon views resource monitoring as two separate tasks: the testing of a condition, and triggering an action upon failure. mon was designed to implement the testing and action-taking tasks as separate, stand-alone programs. mon is fundamentally a scheduler which executes the monitors (each test a specific condition), and calls the appropriate alerts if the monitor fails. The decision to invoke an alert is governed by logic which offers various "squelch" features and dependencies, all of which are configurable by the user.
Monitors and alerts are not a part of the core mon server, 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 necessary, the mon server does not need to be changed. This makes mon easily extensible.
ABOUT |
Some features that mon 0.99.2 offers. |
NEWS |
The latest release notes and other news. Last updated Thu Jun 17 13:36:01 EDT 2004 . |
CONTRIB |
Archive of user-submitted contributions (monitors, alerts, clients, etc.) |
FAQ |
Frequently Asked Questions about mon |
LIST |
Mailing list information |
BUGS |
How to submit bugs and suggest features |
MONITORS |
Monitor scripts which are included |
ALERTS |
Alert scripts which are included |
CONFIG |
An example configuration script to give you an idea of what mon can do. |
MANUAL |
Manual pages for current release |
DEVELOPMENT |
CVS access to mon source code |
FTP |
Obtaining the current version via FTP Please use a kernel.org mirror. The path is /pub/software/admin/mon. Stable: 0.99.2 Development: see the latest code in CVS on sourceforge.net. |
Jim Trocki
and generated with m4
6d5bbb4d