I'm exceptionally busy, so I apologise for the short response. Here it is in psuedo-code (copied from our application, snipped for brevity to highlight the point). All our servlets extend from one base class, so this service method is the first entry point for all requests on our web-application: snippet from our log4j configuration file: .... <appender name="File" class="org.apache.log4j.DailyRollingFileAppender"> <param name="File" value="${catalina.home}/logs/lhr.log" /> <param name="Append" value="true" /> <param name="DatePattern" value="'.'yyyy-MM-dd" /> <layout class="org.apache.log4j.PatternLayout"> <param name="ConversionPattern" value="[%d{ISO8601} %-5p][%20.20c][%t][%X{IPAddress}][%X{UserID}] %m%n" /> </layout> </appender> You notice that in the pattern we output 2 MDC vars, IPAddress and UserID. Here is how they are set & cleared: protected void service(HttpServletRequest req, HttpServletResponse resp) { ............. MDC.remove("UserID"); MDC.remove("IPAddress"); MDC.put("IPAddress", req.getRemoteAddr()); ... HttpSession session = req.getSession(); ... Integer userId = (Integer) session.getAttribute("UserId"); MDC.put("UserID", userId); try { ..... // do web request }... That's it. All request and all it's associated logging events from any class touched as part of this request are now 'tagged' with the UserID and IPAddress. All the other classes that do any logging do not need to worry about context, because the current Thread has been 'tagged' by the MDC. It looks like this in the logs: [2005-12-16 08:57:31,310 INFO ][he.AconexCacheLoader][http-8080-Processor4][192.168.0.242][28] get(fqn): fqn=/Preference/110, operation took 255ms From this I can see the IP address and the userid that generated this single log statement. If I want to correlate all logging events for a userid or IP Address range, one can just grep the logs (or use Chainsaw to filter) I hope that helps,that's as much as I have time for right at this moment (working on 5 hours sleep at the moment). Paul Smith |
smime.p7s
Description: S/MIME cryptographic signature
