[
https://issues.apache.org/jira/browse/LOG4J2-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16894921#comment-16894921
]
Ralph Goers edited comment on LOG4J2-2665 at 7/29/19 4:32 AM:
--------------------------------------------------------------
You can already do part of this.
public void info(Message msg) does exactly the same thing. Just create a
DescriptionMessageBuilder class and use it like:
{code:java}
logger.info(DescriptionMessageBuilder.withFormat("{} was able to
login").withParameter(userid).withDescription("abcd).build());{code}
What you won't be able to do is generate the descriptionId at compile time or
verify it is a valid id at compile time. But the DescriptionMessage could
certainly format the output the way you are asking.
This is actually the whole point of supporting the Message interface instead of
just allowing Strings.
was (Author: ralph.go...@dslextreme.com):
You can already do part of this.
public void info(Message msg) does exactly the same thing. Just create a
DescriptionMessageBuilder class and use it like:
{code:java}
logger.info(DescriptionMessageBuilder.withFormat("{} was able to
login").withParameter(userid).withDescription("abcd).build());{code}
What you won't be able to do is generate the descriptionId at compile time or
verify it is a valid id at compile time. But the DescriptionMessage could
certainly format the output the way you are asking.
> 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)
