You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2019/02/03 04:38:00 UTC
[jira] [Work logged] (LOG4J2-2523) log4j-web should support
header+attributes lookup
[ https://issues.apache.org/jira/browse/LOG4J2-2523?focusedWorklogId=193746&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-193746 ]
ASF GitHub Bot logged work on LOG4J2-2523:
------------------------------------------
Author: ASF GitHub Bot
Created on: 03/Feb/19 04:37
Start Date: 03/Feb/19 04:37
Worklog Time Spent: 10m
Work Description: rgoers commented on issue #246: [LOG4J2-2523] adding support for request related lookup web module
URL: https://github.com/apache/logging-log4j2/pull/246#issuecomment-460022526
This code can only be applied to 3.0 as it contains Lambdas.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 193746)
Time Spent: 20m (was: 10m)
> log4j-web should support header+attributes lookup
> -------------------------------------------------
>
> Key: LOG4J2-2523
> URL: https://issues.apache.org/jira/browse/LOG4J2-2523
> Project: Log4j 2
> Issue Type: New Feature
> Reporter: Romain Manni-Bucau
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Since log4j has a filter it can read headers and attributes from the request and not limit itself to the context. This is quite useful to track a correlation id without any glue code to do.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)