What do you want to monitor?
Mostly I just want to make sure everything is up. We have lots of little applications on a variety of servers and platforms, and most of them aren't being actively developed, so we forget they are even there. So I'm mostly concerned that the Apache servers are up, the database is up, and everything is responding. Things like disk space, server load, runaway processes, etc. would of course be very useful, but I'm hoping to avoid as much infrastructure burden as possible. It should also allow each application to do internal tests; i.e., fetch a page and look for text that indicates an error, then email the entire page if there is an error.
Well, honestly, I'm the programmer, so I'm concerned about the applications being up, because I feel more responsible for that. But we should probably be just as concerned about the rest of it. I just don't want to have to worry about any of this stuff -- let the computer worry, and notify me when there's a problem.
As I think about it, David's suggestion of mon seems good, maybe even combined with the kind of scripts you've been writing (since mon just runs programs for its monitors).
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
