[
https://issues.apache.org/jira/browse/LOG4J2-1724?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alexander K. updated LOG4J2-1724:
---------------------------------
Description:
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
was:
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
> 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.
>
> 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
