Difference between revisions of "Alert notifications"
Jump to navigation
Jump to search
m |
|||
Line 17: | Line 17: | ||
* [[Vserver watchdogs]] -> cron |
* [[Vserver watchdogs]] -> cron |
||
====Jabber/SMS alerts==== |
====Jabber/SMS alerts==== |
||
+ | You can use sendxmpp |
||
+ | |||
+ | apt-get install sendxmpp |
||
+ | echo "Here is a very cool notification agent"|\ |
||
+ | sendxmpp -u <user> -p <passwd> -j <server> -s <subject> <destinataires> |
||
+ | |||
* Hardware damages |
* Hardware damages |
||
** temp, fans |
** temp, fans |
Revision as of 10:56, 26 April 2007
This is a generic page about reporting all kind of misbehaviours from a server.
This is draft, to be implemented :-)
Data collection
What to filter for what kind of alert?
Mail alerts
- Syslog -> Logcheck
- We should send also at least what we want to report via jabber/SMS
- Vserver watchdogs -> cron
Jabber/SMS alerts
You can use sendxmpp
apt-get install sendxmpp echo "Here is a very cool notification agent"|\ sendxmpp -u <user> -p <passwd> -j <server> -s <subject> <destinataires>
- Hardware damages
- temp, fans
- raid
- Software damages
- HD capacity
- CPU load 100% for more than X mins
The easiest is to take the third field of /proc/loadavg which is a mean over the last 15 mins, here with 2 CPUs:
awk '$3 > 2 {print "alert"}' /proc/loadavg
- network load > X for more than Y mins
- exim load > X mails sent per min