Click here to Skip to main content
65,938 articles
CodeProject is changing. Read more.
Articles
(untagged)

ELWEA - EventLog WebEvent Aggregator for ASP.NET

0.00/5 (No votes)
28 Apr 2011 1  
Keep an ASP.NET web application error tracking isolated and easily accessible

Last time, I wrote about Health Monitoring was during 2008, and since then I've been 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 for me to start thinking about releasing a version of my EventLog WebEvents aggregator.

I’m now happy to announce that I finally made this project available at CodePlex and named it: ELWEA - EventLog WebEvent Aggregator for ASP.NET.

While different in nature, this project's 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 information. This project's main goal is to aggregate all EventLog data belonging to a specific web application under a specific EventLog source name.

I’m sure that web developers and web site administrators will love it but I think that IT pros that manage shared hosting environments will fill it useful too.

Visit here for a more complete description and here for the project documentation.

To make your life even simpler, I’m planning to make a NuGet package available for ELWEA. Keep an eye on this.

Enjoy it!

License

This article has no explicit license attached to it but may contain usage terms in the article text or the download files themselves. If in doubt please contact the author via the discussion board below.

A list of licenses authors might use can be found here