On Tue, Nov 24, 2009 at 02:50:51PM -0500, Jeremy wrote: > Sherif Zaroubi wrote: > > I need to monitor these jobs, by monitor I mean: > > - Failed to execute (Cron was supposed to run but didn't)
That should never happen unless the cron daemon is crashed, which can be
monitored with nagios or monit. I very rarely need to monitor this.
> > - Failed in it's execution (Cron job reported errors)
That should be handled through the script and cron itself: cron jobs
should be silent unless there's a failure, in which case cron will send
you an email.
> > - Execution took too long (Cron job took more than x% of time than
> > normal)
That should be taken care of by the script launched by cron, which
should watch itself by using alarm() or another mechanism to kill itself
after N time.
I think that parsing logs is not the right solution to your problem, but
then if I would, I would use logcheck. ;)
A.
--
Ce que les siècles des grands abatoirs nous aura appris
Devrait être inscrit au fond de toutes les écoles;
Voici l'homme: le destructeur des mondes est arrivé.
- [no one is innocent]
signature.asc
Description: Digital signature
_______________________________________________ mlug mailing list [email protected] https://listes.koumbit.net/cgi-bin/mailman/listinfo/mlug-listserv.mlug.ca
