Re: Distributed Logging Experiences
log4net has a RabbitMQ appender, so that messages go to a RabbitMQ queue. http://nuget.org/packages/log4net.RabbitMQAppender http://www.rabbitmq.com/ Maybe that will help you? Regards, Tristan. On Fri, Apr 6, 2012 at 11:20 PM, Dave Walker rangitat...@gmail.com wrote: Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker
Re: Distributed Logging Experiences
Looks good.. Cheers will let you know how we get on On 19 Apr 2012, at 03:41, Tristan Reeves tree...@gmail.com wrote: log4net has a RabbitMQ appender, so that messages go to a RabbitMQ queue. http://nuget.org/packages/log4net.RabbitMQAppender http://www.rabbitmq.com/ Maybe that will help you? Regards, Tristan. On Fri, Apr 6, 2012 at 11:20 PM, Dave Walker rangitat...@gmail.com wrote: Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker
Distributed Logging Experiences
Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker
Re: Distributed Logging Experiences
I've seen people use msmq to write a log entry locally and have it read from the local machine into a centralized location, but that was on a system with only about 20 web nodes. I've also seen ppl write to the windows event log, and use monitoring tools like SCOM to aggregate (also on about 20 nodes). I'm curious to know what you're doing that requires that many nodes. I know a lot of household name web sites that run on a 10th or 20th of that. Sent from my iPhone On 06/04/2012, at 11:20 PM, Dave Walker rangitat...@gmail.com wrote: Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker
Re: Distributed Logging Experiences
I wonder if this could be easily extended to a cloud solution. MSMQ locally and then HTTP offsite to an EC2 type beast to aggregate and correlate On 7 April 2012 10:35, Joseph Cooney joseph.coo...@gmail.com wrote: I've seen people use msmq to write a log entry locally and have it read from the local machine into a centralized location, but that was on a system with only about 20 web nodes. I've also seen ppl write to the windows event log, and use monitoring tools like SCOM to aggregate (also on about 20 nodes). I'm curious to know what you're doing that requires that many nodes. I know a lot of household name web sites that run on a 10th or 20th of that. Sent from my iPhone On 06/04/2012, at 11:20 PM, Dave Walker rangitat...@gmail.com wrote: Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker -- regards, Preet, Overlooking the Ocean, Auckland
RE: Distributed Logging Experiences
What other technologies do you have in the mix already? What is doing the aggregation/reporting? As Joseph mentioned, you could write to a Windows Event Log, and then use SCOM, Syslog client or even native Windows event forwarding, to send that to a central location (depending on what the central target is). You could write to a text file and use a client to send that to a central syslog server or SQL Server. MSMQ is another option. Cheers Ken From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On Behalf Of Dave Walker Sent: Friday, 6 April 2012 9:21 PM To: ozdotnet@ozdotnet.com Subject: Distributed Logging Experiences Hey guys, looking for ideas or proven experiences involving logging from larger applications e.g. 200+ web nodes. Our current system of log4net into files on each server is quickly proving to be a nightmare - We are struggling to find out when, where, how and why things are breaking because of the rapid growth we have experienced. E.g. things we have thought about include log4net into a DB that we can pull into a centralised location, MSMQ, file watchers etc. What have you guys done in the past? Thanks, Dave Walker
