[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15728198#comment-15728198 ]
Alexander K. commented on LOG4J2-1724: -------------------------------------- Yes, I will do it. The reason of doing this on 2.6.2 is that the latest Spring Boot Log4j2 release is integrated with this version and they are going to upgrade to Log4j 2.7 only in the next major release and this will take couple of months. > 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 > > > 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