Although many IIS and related errors are written to the Event Log on the local machine, HTTP errors are typically reported to IIS's own log file. This is often a rolling file based on the current date.

With the Sentry-go Quick IIS Web Server Monitor, you can be notified of  errors written to this file (e.g. HTTP 404 - Page Not Found, HTTP 500 - Server error) based on both preloaded & configurable keywords or phrases. 

  Why Monitor the IIS Log File ?
 
Even Microsoft's own applications such as IIS write some of their errors to different locations. Many are logged via the Event Log system but others use their own text-based log files. Despite not being in the Event Log, it can be crucial to be aware of errors written to these files - e.g. to determine when a user has received an error from your site, there's a broken link or unavailable file. Continual problems, that you are unaware of will soon mean your customers will go elsewhere. 
  
With the Sentry-go Quick IIS Web Server Monitor, you can quickly and easily monitor the IIS log file out of the box. Simply define the file, adjust the keywords provided (if you wish to add more) and let Sentry-go do the rest. When an error is written to the file, the webmaster and/or support teams can be notified immediately using the many alerting options available. 
 
Monitoring this file takes just a few steps. Simply tell the Quick Monitor you wish to monitor the IIS log file, tell it the location of the file, check or amend the supplied keywords (normally HTTP error numbers) and let Sentry-go do the rest!