Creating a centralized exception registration system

Question

I plan to create a centralized logging system for my application. My application contains several separate applications that run on different client machines. I planned to start using the exception handling block from the Enterprise Library. It looks very cool and does exactly what I need, creating event logs due to exceptions. The question is, I would like to create these magazines in one place. Therefore, when client computers are in the same domain, they will create logs in the domain controller's event logs. Has anyone seen good articles about this or any other good ideas about creating a centralized journal system?

EDIT: I'm talking about C # and Windows OS.

Answer 1

If you could narrow your OS to Win7 and Win 2008 R2 ...; -)

There is a built-in function for forwarding and collecting events (Win7, Win2008 R2 and, possibly: Win 2008 R1, Vista): http://www.sysadminlab.net/windows/forward-event-log-from-several-server-to-a -central-windows-2008-server

There are some differences from Win 2008 R1 (in the community comment): http://technet.microsoft.com/en-us/library/cc748890.aspx

BTW. I have not tried this in practice, but overall I see HUGE improvements in Windows 2008 R2 registration, diagnostics, etc. Recently, Microsoft has been doing a lot of good in these areas.

Answer 2

With ELMAH, I found this article that talks about registering from multiple applications in one place on SQL Server.

If you want to use log4net, you can use RemotingAppender or UDPAppender to log in to the central server.

You can also configure the Syslog server, Kiwi for Windows.

In addition, some third-party solutions, such as Exceptioneer , which integrates with ELMAH or services offering such as BugCollect

Answer 3

It would probably be helpful to know which OS and programming language you are using. For example, Rails applications can use services such as Airbrake and Exceptional to track exceptions. There may be such a service for any language that you use.

If your application is configured to log on to syslog, there are many interesting ways to configure various system logs to log on to the central host. FreeBSD syslog can easily be configured to log on to a remote host , as well as Debian . Most Unixes probably have information about this; This article discusses many options and alternatives on Linux. I heard very good things about Splunk . It is not specifically designed to run exception logs, but it must use some intelligence to categorize problems and provide you with aggregate data on how often certain types of problems occur and something like that.

Hope this helps!