Details
-
Task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.6.0, 3.0.0-alpha-4, 2.5.3, 2.4.17
-
None
-
None
Description
Tracing the distributed actions of ProcedureV2 RemoteProcedure execution is painful. We are pretty good about logging the proc_id most of the time, but we don't catch them all. Now that we're up on log4j2, let's use the MDC feature to include some basic information universally.
Attachments
Issue Links
- relates to
-
LOG4J2-3660 PatternLayout %notEmpty should consider an MDC with no keys as empty
- Closed
- links to
(1 links to)