Hi,
is there a particular reason why RFC5424Layout#getProcId() always returns
an undefined value (i.e., "-")?
On most VMs, java.lang.management.ManagementFactory.getRuntimeMXBean().getName()
returns @, so maybe the code could be changed like this:
private static final String PROCESS_ID;
static {
onversion specifiers with $$ as I
can with %X
Would you consider accepting a patch that adds support for slf4j-like default
values
in %X{key} and %K{key}, s.th. like %X{key:-defaultValue} ?
Regards,
Oliver
>
>> On Sep 30, 2013, at 8:04 AM, Oliver Flege wrote:
>>
>> ok, thi
gt; of your configuration. Then when you specify something like ${sys:foo} if foo
> is not defined as a system property the default value will be used,
>
> Ralph
>
>> On Sep 30, 2013, at 3:30 AM, Oliver Flege wrote:
>>
>> Hi,
>>
>> I am considering to swi
Hi,
I am considering to switch from slf4j/logback to log4j2;
in slf4j/logback, I can specify a default value for a missing mdc entry
like this:
%d{HH:mm:ss} %X{FOO:--} %c{0} - %m%n
which would print "-" if mdc.get("FOO") is null (the ":-" separates
the key and the default value).
Having a defi