In article <[log in to unmask]>,
Tom Brandt  <[log in to unmask]> wrote:
>
>For reasons that are not at all clear to me, ASP occassionaly stops
>working. (Microsoft's cryptic and downright misleading messages are no
>help). We usually are not aware that ASP has stopped working, and the sites
>therefore not functional, until a user complains.

>Does anyone out there have any ideas of how to automate monitoring of the
>sites so that if a site, or a part of it, stops functioning, someone who
>can respond right away is notified by e-mail or some other mechanism?
>
Win2k will do this automagically as part of IIS 5.  At my work, we use
Keynote Redalert (www.redalert.com) to check our site remotely, and we've
created several test pages that run a simple ASP to say the service is
working as well.  You could then have RedAlert send a page/email to
something that could automate the restarting.  (Agent in Notes/have
procmail fire off some processes that would ultimately do a service restart
in NT, etc.)

It works quite well for us, but for allof our sites and the services we use,
it's about $120/month.

There are some products you can buy for WinNT4 that can sit on your
webservrs and monitor services and restart them if necessary, but since we
needed external detection, we went with a service.  WEbTrends, which also
monitors weblogs and does excellent reporting, has a bunch of utilities in
the Professional suite that do this.

Rich Frueh
Systems Administrator
WHEDA
[log in to unmask]

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *