You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Alexander K. (JIRA)" <ji...@apache.org> on 2016/12/07 06:58:58 UTC
[jira] [Comment Edited] (LOG4J2-1724) Using variables in
GelfLayout's additional fields at runtime
[ https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15727931#comment-15727931 ]
Alexander K. edited comment on LOG4J2-1724 at 12/7/16 6:58 AM:
---------------------------------------------------------------
The patch based on version 2.6.2 is attached.
was (Author: alexkra@amdocs.com):
The patch is attached.
> 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-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org