Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I would like to know if there is a way, like a logging option in IIS to keep track of when the server or a site is up or down, so that when you get a client saying the service was down, you can go and check at that time and date and know if it was the server or the site, or something else....

Thanks for the help

share|improve this question
    
This all depends on what caused the server or site to go down. An administrator stopped the site? The server froze? IIS logs some of this already, and for other things it's impossible to for it to log (if the server froze for example). What are the current causes of your server/site downtime? –  Izzy Sep 15 '10 at 16:55

2 Answers 2

Good free service: http://mon.itor.us/

The problem with doing all the monitoring locally is you won't be aware of any network problems which might arise.

share|improve this answer
    
I believe the OP is wanting to look at logs that specify what was at fault, not a list of uptime/downtime... –  Josh Brower Sep 15 '10 at 16:54
    
Fair call. However, the OP should realise that server/service monitoring is something that generally comprises a lot of different components. External monitoring is one of them. Another is the service's log files. A third component is something like cacti or nagios. –  wolfgangsz Sep 15 '10 at 16:59
    
Agreed, which is I said doing ALL the monitoring locally, implying he should still monitor locally, but this will provide additional insight. –  Kyle Buser Sep 15 '10 at 17:36

I don't know if there is an easy native way to do this in IIS (I am mostly a Linux admin), but I have set up a nagios installation that I think does what you are looking for. I do routine pings and also http requests of all of my webservers (and individual sites on the those servers). You can even set up an "expected r can geneesult" of an http request if you want to check for DB connectivity, etc. That way Irally go back through nagios logs and can tell what it is that failed. The trick is to make sure that you have enough local vs. remote monitoring that you can tell the difference between a server failure and a network failure.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.