From: Yves <yme...@pe...> - 2004-12-07 13:11:22
|
> All, > > I'm trying to see what the best way is of monitoring perfparsed, > preferably using nagios itself. I'm currently using perfparsed in > combination with the write to pipe method. > > What are my options? > > 1. check_procs -c1:1 -C perfparsed -u nagios > this will notify me in case the daemon died. I could attach an event > handler to restart the perfparse daemon. > The problem with this method is that there is no way of knowing the > perfparse daemon is still doing anything useful, since nagios writes > to a named pipe, and this never fails. (and even then, should it fail, > there's apparently no trace of the failure anywhere). This hasn't > happened (yet), the daemon seems to die whenever something goes wrong. > > 2. write a (perl) check script that checks the perfparse_service_bin > (since I'm storing in a mysql db) for new data (i.e check the > timestamp of the most recent record, cry wolf if it's older than x > minutes). Attach an event handler to check for perfparsed still > running and eventually restarting it. In my view this is the only > right way to check the sanity of perfparse. > > I'd like to hear your thoughts on this, or any other ideas.... What about a plugin that does both ? Do you think that adding some "watchdog" function to perfparsed would be = a good idea ? I mean adding some "touch /var/lock/some.perparse.lock" feature in the main= loop. Your plugin could test that file mtime :) When perfparsed breaks, if you can find the reason, tell us, and we'll tr= y to find a way to make perfparsed do something else than break. Yves --=20 - Homepage - http://ymettier.free.fr - http://www.logicacmg.com - - GPG key - http://ymettier.free.fr/gpg.txt - - Maitretarot - http://www.nongnu.org/maitretarot/ - - Perfparse - http://perfparse.sf.net/ - |