[MAGNOLIA-2294] Provide mapped diagnostic context variables Created: 03/Aug/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: core
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Philippe Marschall Assignee: Philipp Bärfuss
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Java Source File MappedDiagnosticContextFilter.java    
Issue Links:
duplicate
duplicates MAGNOLIA-2635 Trace current URL/userid for logging Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

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.



 Comments   
Comment by Magnolia International [ 07/Apr/09 ]

This was already partially implemented with MAGNOLIA-2635 although this looks like a better impl.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 03:35:19 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.