I have used the Trace subsystem and it works fine for relatively simple scenarios. What I'm really looking for is a logging/tracing/possibly instrumentation framework with pretty comprehensive log viewing capabilities. Like I said, I've looked at MS Logging and Instrumentation app block and Log4Net. Of those two, I'd say that the MS Logging and Instrumentation app block is the closest. But it does have some "issues" like the queue implementation and the ties to the Config app block. Where all the frameworks I've looked at seem to fall short is in the "comprehensive log viewing" respect.
WRT persistence og log data. There was a suggestion to leave the logs distributed i.e. on the local server where the application is generating log items and then collate the data for viewing via something like MOM. While strategy potentially lessens the failover issues that are inherient in log data centralization the benefits would have to be high because enterprise-wide MOM installations could be an expensive undertatking. It still makes sense to me to consider centralizing the log data, of course taking into account fail-over and performance issues and then twisting the collected viewable output based on attributes that are attached to each log item ... like servername, timestamp, maybe an operation that is scoped by a GUID that is centrally obtainable. Again, if there's a COTS product that can fulfill most of these requirements I'd be interested in some details. Regards =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
