I agree, a filter would be good, but still, to get it right might take some serious tuning.
If you are not doing this for security/alerts, you can go and get an access log analyzer. There are tones of analyzers out there. If all fails, /xusage is still going to be there. And if your website becomes hugely successful, at that point of course you can get someone to develop it:). -Yan -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 03, 2004 1:23 AM To: Tomcat Users List Subject: Re: access log Hi Yan, I'm only writing the access logs to a DB, I'm not too interested in keeping the normal logs as long as everything runs peachy. There is actually a small comment in the JDBCAccessLogValve noting that it would be good to develop a filter on the mime type - with which one could just drop all the image request log statements, for instance. However all the fuss about bottlenecks is all pie-in-the-sky for me, unless my website becomes hugely successful. At that point of course I'll just hire someone to develop it ;) Adam On 02/02/2004 11:36 PM Yansheng Lin wrote: > Hi, How about just log errors and warnings to the db? So for other types of log > entry, it will still be file based; but when there is an error or a warning, in > log4j, you set it up so it writes to two places. I don't notice any performance > issue with this setup. But just want to confirm. > > Thanks! > > -Yan > > -----Original Message----- > From: Shapira, Yoav [mailto:[EMAIL PROTECTED] > Sent: Monday, February 02, 2004 11:53 AM > To: Tomcat Users List > Subject: RE: access log > > > > Howdy, > > >>re: asynchronous DB writes - Tim pointed out the JDBCAccessLogValve. I >>assume you are thinking that this would quickly become a bottleneck? > > > Yeah, that's what I'm thinking. Writing the access log valve should be > very very quick, very very scalable, or it easily becomes a bottleneck. > Remember, for example, that a single page request with 9 images is 10 > access log writes. 10 users asking for that page concurrently means 100 > concurren access log writes, etc etc. > > Yoav Shapira > > > > This e-mail, including any attachments, is a confidential business > communication, and may contain information that is confidential, proprietary > and/or privileged. This e-mail is intended only for the individual(s) to whom > it is addressed, and may not be saved, copied, printed, disclosed or used by > anyone else. If you are not the(an) intended recipient, please immediately > delete this e-mail from your computer system and notify the sender. Thank you. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- struts 1.1 + tomcat 5.0.16 + java 1.4.2 Linux 2.4.20 Debian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
