Distributed Logging and Tracing for .Net

nitro

nitro

Does anyone have a recommendation for a library that allows a distributed application logging and tracing, and with a viewer to view the logging in realtime. Being able to sort messages by machine etc on the viewer would be nice, etc?

For .Net 2.x or later.

I am using the Enterprise Library 2.0 Logging Application Block

http://codebetter.com/blogs/david.hayden/archive/2006/02/19/138644.aspx

but AFAIK, this doesn't work very well in a distributed environment.

The less intrusive on the code the better, so that my code looks the same (with maybe a decorator to the class) so that exceptions, debug/trace are automatically logged to the distributed logging system.
 
Quote from jmjatlanta:

Use Log4Net and their SQL database appender. Then you can use SQL to get the info you need. Just a suggestion.
More...
Thanks. That's not a bad idea. To see it in realtime you would probably go one further and use triggers.

I couldn't believe there was nothing like this, so I wrote a very quick server that different clients can send (multicast) debug/ trace information to. The right way to do it is to use system.diagnostics and override the trace functions. That way when you are in the debugger, your code will send information to it, and during runtime ("release"), to this scheme that I describe above. For now this is ok.
 
i log to a messaging queue using a log4net appender. but the log viewing is just a web page. i havent seen anything worth buying
 
For the most scalable distributed logging, I would use the Enterprise Library but with an MSMQ (Microsoft Message Queuing) trace listener, and I would then get a process to handle items arriving on that queue.
MQs can handle redundancy, mirroring, filtering, persistance and are the most scalable technology to date in my opinion.
 
Quote from Big:

For the most scalable distributed logging, I would use the Enterprise Library but with an MSMQ (Microsoft Message Queuing) trace listener, and I would then get a process to handle items arriving on that queue.
MQs can handle redundancy, mirroring, filtering, persistance and are the most scalable technology to date in my opinion.
More...
Another good idea. For those that are lost,

http://www.15seconds.com/Issue/020910.htm
 
Quote from rosy2:

i log to a messaging queue using a log4net appender. but the log viewing is just a web page. i havent seen anything worth buying
More...
Thanks.

Yeah, appenders to log4net seem to be a popular idea.
 
You must log in or register to reply here.
Back
Top