http://mon.itor.us

recommend to me by Chris Blankenship

Here are a few things I have come across with regard to the event log. These are really for general interest because they really shouldn’t matter for your typical BE.Net usage. This is, as you say, more for enterprise level considerations.

– Event logs usually have size limits, which if reached, old records fall off the end of the log.
– A guy at work also found that the event log started to struggle at about 800 records/second on our test hardware
– SCOM is great for monitoring event logs, but it the event log agent doesn’t seem to look at records that already exist in the log when the agent starts (so you may miss some records).

🙂

This is a good idea, but be careful when sending this kind of information by email.

If the errors occur a lot, you are going to get spammed badly with the same information.

I used to work for a company that used this idea. One day the mail server went down because 90,000 emails were generated due to the same error. The main problem with this solution is that you can’t control the frequency. Unfortunately they didn’t learn and a few months later they killed themselves again with around 75,000 emails.

The other issue with this is that email is not encrypted and you could be sending sensitive information about your site via email.

I would like to see this type of functionality rolled into BE, probably as an extension.