I don't know how common this so I'll just post it. If we have an error in the log of Magnolia one of the first things to do is trying to figure out what the user was doing. Sometimes this can be deduced directly from the stack trace, sometimes it is harder. In the harder cases we in general need to know the request URL and remote address. Which means heading over to the transfer.log which is tedious. It would be tremendously helpful if we had this information in the Magnolia log. But we don't want to change every log statement. MDCs address this problem in a simple and elegant way.

A sample class is attached with an extensive class comment that explains how to use it. Right now it provides only very few information, but it is a starter.