[OAK-6720] The path should be included in the TRACE log of reads

• Type: Improvement
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 1.7.8
• Component/s: core
• Assignee: Unassigned
• Reporter: Joerg Hoh
• Created: 26/Sep/17 14:11
• Updated: 20/Oct/20 13:37

Description

When I enable the TRACE logging of read requests (setting org.apache.jackrabbit.oak.jcr.operations.reads to TRACE) I get this result:

26.09.2017 15:39:15.530 TRACE [0:0:0:0:0:0:0:1 [1506433155519] GET /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads [session-2620413] getValue
26.09.2017 15:39:15.530 TRACE [0:0:0:0:0:0:0:1 [1506433155519] GET /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads [session-2620413] getItemOrNull
26.09.2017 15:39:15.530 TRACE [0:0:0:0:0:0:0:1 [1506433155519] GET /foo.html HTTP/1.1] org.apache.jackrabbit.oak.jcr.operations.reads [session-2620413] hasProperty

It would be good if the path where this read operation happens, would be logged as well. As it is on TRACE level and should be rarely used, even a performance impact would be acceptable.

Issue Links

• is related to: OAK-9254 Logging for JCR API calls