Thanks for the valuable opinions. Based on your opinions, I have some additional questions and clarifications.
Performance and availability of a logging queue Using a log queue should not be a "bottleneck" issue as its log message processing is asynchronous. Question: By failover are you referring to failure of the server that hosts a logging queue? If so, that is an issue but it can be addressed; albeit not as easily as I'd like. I am also looking at the least amount of heartache wrt to architecture. Good point. MOM to aggregate logs If MOM can be used to easily perform the message aggregration from physically dispersed logs (without a lot of maintainance) then that's an option worth assessing. Thanks. However, another issue that physical centralization of logs addresses is maintainance of logs; meaning periodic off loading or cleaning of logs as they are not physically dispersed to each server ... if they are eventually logged to files anyway. Using a database to hold logs is a great option. It definetely covers any log message aggregation and sorting/filtering requirements. But it too has the tendency of suffering from availibility issues at the worst time; when your're having problems getting a new server up and running with a newly installed app and there are database server connectivity issues. Sometimes logs can be used to solve the problem. Clustering scenarios "Again, let me know what clustering options you are looking at and I can reply with some more definitive suggestions." Addressing clustering. I guess I maybe naively meant that "filtering the view" would be the mechanism to aggregate log messages from several servers in a cluster. We just have a couple of NLB sets of 2 to 3 servers but not all app servers are even load balanced. How would you propose aggregating the log messages for NLB servers? Of course, this is a very important requirement. I would very much like the benefit of some experience here. Using a remote private queue I really want to avoid any AD entanglements if possible. i.e. public queues but it's still an option. Remote private just refers to the way the queue is referenced. If MOM will easily allow private server log queues to be aggregated then this is an option. Regards =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
