[ 
https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15729363#comment-15729363
 ] 

Ralph Goers commented on LOG4J2-1724:
-------------------------------------

An ICLA is not required for patches. It is requested for larger contributions 
and it is required for a person to become a committer.  The reason for this is 
that when someone provides a patch then they are implicitly agreeing to provide 
the patch under the terms of the Apache license and are indicating that it is 
their own work. We request the CLA for larger contributions to confirm that the 
individual has the right to contribute it as it is more likely others may have 
helped. 

> Using variables in GelfLayout's additional fields at runtime
> ------------------------------------------------------------
>
>                 Key: LOG4J2-1724
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-1724
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Layouts
>    Affects Versions: 2.6.2, 2.7
>            Reporter: Alexander K.
>            Assignee: Mikael Ståldal
>         Attachments: patchfile.txt, patchfile.txt
>
>
> Hello,
> I would like to suggest the following improvements for GelfLayout:
> 1. Using variables in additional fields at runtime. For example resolving 
> "value": "$$\{ctx:key\}" at runtime as it is done in other places. Thus, 
> custom lookups will be available as well.
> 2. Having an indicator includeThreadContext to control whether the contents 
> of the ThreadContext should be included. Sometimes it is usable to include 
> only some of its values and then it will be available using the first 
> suggested improvement by specific variable resolution.
> 3. Resolving HOST attribute in case it is not provided by using for example 
> InetAddress.getLocalHost().getHostName().
> Regards,
> Alexander



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org
For additional commands, e-mail: log4j-dev-h...@logging.apache.org

Reply via email to