Last time I wrote about Health Monitoring was during 2008 and since then I ‘m using, on a daily basis, a complex Health Monitoring EventLog provider to aggregate WebEvents from specific ASP.NET web applications.
Last year I found ELMAH (Error Logging Module and Handler) project and became a fan of the concept:
“[…] facility that is completely pluggable. It can be dynamically added to a running ASP.NET web application, or even all ASP.NET web applications on a machine, without any need for re-compilation or re-deployment.”
It didn’t take much time until I start thinking about releasing a version of my EventLog WebEvents aggregator.
While different in nature this project main goal is pretty similar to the ELMAH project: keep an ASP.NET web application error tracking isolated and easily accessible.
What makes this project different from many other like ELMAH is the fact that it’s not focused on handling and persisting error info. This project main goal is to aggregate all EventLog data belong to a specific web application under a specific EventLog source name.
I’m sure that web developer and web site administrators will love it but I think that also IT pros that manage shared hosting environments will use it.
To make your live even simpler I’m planning to make a NuGet package available for ELWEA. Keep an eye on this.