jabowery has asked for the wisdom of the Perl Monks concerning the following question:
I'm thinking of writing a system monitor that goes through and checks a bunch of critical system states so that when anything critical changes, an email is fired off.
An obvious way of doing this would be to have a timed loop that calls configurable vector of status check routines/command lines, returning the associated state vector, and then seeing which, if any, of the states changed since the last time through and firing off an email containing those changes.
What is the best practice for this kind of thing?
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Alerting On Critical State Changes
by Your Mother (Archbishop) on Mar 25, 2015 at 03:16 UTC | |
|
Re: Alerting On Critical State Changes
by karlgoethebier (Abbot) on Mar 25, 2015 at 09:10 UTC | |
|
Re: Alerting On Critical State Changes
by afoken (Chancellor) on Mar 25, 2015 at 06:49 UTC | |
|
Re: Alerting On Critical State Changes
by LanX (Saint) on Mar 25, 2015 at 12:07 UTC | |
|
Re: Alerting On Critical State Changes
by GotToBTru (Prior) on Mar 25, 2015 at 03:12 UTC | |
|
Re: Alerting On Critical State Changes
by Anonymous Monk on Mar 25, 2015 at 03:22 UTC | |
|
Re: Alerting On Critical State Changes
by sandy105 (Scribe) on Mar 26, 2015 at 11:48 UTC |