[
https://issues.apache.org/jira/browse/LOG4J2-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894904#comment-16894904
]
Ralph Goers commented on LOG4J2-2665:
-------------------------------------
How does putting a hash into the log make it more understandable? Where I work
all the logs look like:
{code:java}
2019-07-01 17:03:00,884 [http-bio-8081-exec-36] INFO
{requestId=c1790b52-9c5c-11e9-82a9-005056a3043e,
sessionId=bda0b311-9c5c-11e9-82a9-005056a3043e, loginId=tomthumb, userId=11111,
ipAddress=192.168.10.1, corpAcctNumber=12345}
c.n.a.s.i.UserServiceImpl.getAccountManager:36 - Subscriber Id: 22222{code}
This takes ThreadContextMap fields and automatically adds it to the logs. See
[http://logging.apache.org/log4j-audit/latest/requestContext.html] for a
discussion of how this works. As you can see though, it is crystal clear to
everyone what the data means. So I am struggling with what you are trying to do
since Log4j already supports lots of features to accomplish this.
> Incident Response Improvement for Log4J
> ---------------------------------------
>
> Key: LOG4J2-2665
> URL: https://issues.apache.org/jira/browse/LOG4J2-2665
> Project: Log4j 2
> Issue Type: Improvement
> Components: API
> Affects Versions: 2.12.0
> Reporter: Joubin Jabbari
> Priority: Major
>
> Issue:
> Logging something to a file only solves half of the problem. The log needs to
> readable and distinguishable by auditors and responders.
> This is a proposal to add a optional feature for the instantiation and
> compile process of the logger.
>
> # Allow for a description parameter for each log statement.
> # When the description is filled out, log events that correspond to that
> description are given a hash number that match the hash of the description
> # The descriptions of said log are extracted and paired with their hash into
> a "log description file" during the compile process
> Example:
> Previous Logging Method
> {code:java}
> logger.info(user.id + " was able to login")
> {code}
> Proposed change
> {code:java}
> logger.info(user.id + " was able to login", description="This log event
> appears right after every user logs in"){code}
> Log File example
> Previous:
> {code:java}
> user132 was able to login
> {code}
> Proposed:
> {code:java}
> c58868be25f925102364ba7cf15b4fbcca5d3f11: user132 was able to login
> {code}
> Proposed log file description file generated during compile time:
> {code:java}
> c58868be25f925102364ba7cf15b4fbcca5d3f11: This log event appears right after
> every user logs in{code}
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.14#76016)
