You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-user@logging.apache.org by Fröstl,
Christian <ch...@accenture.com> on 2018/08/13 16:02:40 UTC
Get thrown_name from JSON appender in RollingRandomAccessFile
appender
Hi everybody,
we are using the log4j2 json appender to generate json logs which will be used in graylog.
The JSON layout doesn’t fit perfectly for us, and I tried to create our own JSON by using the RollingRandomAccessFile appender with the patternLayout and the JSON encoding function.
This fits very good for us, but I am not able to create a field thrown_name, like in the JSON appender.
Example of JSON Appender:
Field name: thrown_extendedStackTrace
Value: org.springframework.beans.FatalBeanException; ......... <the whole stacktrace>
Field name: thrown_name
Value: org.springframework.beans.FatalBeanException
It is no problem to generate the whole stacktrace in patternlayout using this code snippet: enc{%throwable}{JSON}
But how to generate a field which only includes the thrown_name of the exception?
Thanks and greetings,
Christian
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
Re: [External] Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Fröstl,
Christian <ch...@accenture.com>.
If this is not implemented at the moment, is there a possibility to parse for example %rEx{short} with regex or in another way?
Christian
On 15.08.18, 01:55, "Ralph Goers" <ra...@dslextreme.com> wrote:
Is there a reason why you cannot use $ex{short.className} in your pattern?
Ralph
> On Aug 14, 2018, at 2:21 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
>
> On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
> christian.froestl@accenture.com> wrote:
>
>> To be more precise, I only need the name of the exception in a dedicated
>> field like the thrown_name in the JSON layout.
>>
>> Greetings,
>> Christian
>>
>> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
>> wrote:
>>
>> We like to have a local log format and don't like to send all logs
>> directly to the server.
>> Do you have any idea to get this format in a patternlayout?
>>
>> Thanks and greetings,
>> Christian
>>
>> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>>
>> Have you tried out the GELF layout?
>>
>> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
>> christian.froestl@accenture.com> wrote:
>>
>>> Hi everybody,
>>>
>>> we are using the log4j2 json appender to generate json logs
>> which will be
>>> used in graylog.
>>> The JSON layout doesn’t fit perfectly for us, and I tried to
>> create our
>>> own JSON by using the RollingRandomAccessFile appender with the
>>> patternLayout and the JSON encoding function.
>>> This fits very good for us, but I am not able to create a field
>>> thrown_name, like in the JSON appender.
>>>
>>> Example of JSON Appender:
>>> Field name: thrown_extendedStackTrace
>>> Value: org.springframework.beans.FatalBeanException; .........
>> <the whole
>>> stacktrace>
>>>
>>> Field name: thrown_name
>>> Value: org.springframework.beans.FatalBeanException
>>>
>>> It is no problem to generate the whole stacktrace in
>> patternlayout using
>>> this code snippet: enc{%throwable}{JSON}
>>> But how to generate a field which only includes the thrown_name
>> of the
>>> exception?
>>>
>>> Thanks and greetings,
>>> Christian
>>>
>>>
>>>
>>> ________________________________
>>>
>>> This message is for the designated recipient only and may contain
>>> privileged, proprietary, or otherwise confidential information.
>> If you have
>>> received it in error, please notify the sender immediately and
>> delete the
>>> original. Any other use of the e-mail by you is prohibited.
>> Where allowed
>>> by local law, electronic communications with Accenture and its
>> affiliates,
>>> including e-mail and instant messaging (including content), may
>> be scanned
>>> by our systems for the purposes of information security and
>> assessment of
>>> internal compliance with Accenture policy. Your privacy is
>> important to us.
>>> Accenture uses your personal data only in compliance with data
>> protection
>>> laws. For further information on how Accenture processes your
>> personal
>>> data, please see our privacy statement at
>>> https://www.accenture.com/us-en/privacy-policy.
>>>
>>>
>> ______________________________________________________________________________________
>>>
>>> www.accenture.com
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you have
>> received it in error, please notify the sender immediately and delete the
>> original. Any other use of the e-mail by you is prohibited. Where allowed
>> by local law, electronic communications with Accenture and its affiliates,
>> including e-mail and instant messaging (including content), may be scanned
>> by our systems for the purposes of information security and assessment of
>> internal compliance with Accenture policy. Your privacy is important to us.
>> Accenture uses your personal data only in compliance with data protection
>> laws. For further information on how Accenture processes your personal
>> data, please see our privacy statement at
>> https://www.accenture.com/us-en/privacy-policy.
>>
>> ______________________________________________________________________________________
>>
>> www.accenture.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
Re: [External] Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Fröstl,
Christian <ch...@accenture.com>.
Thanks, ticket opened: https://issues.apache.org/jira/browse/LOG4J2-2410
Christian
On 15.08.18, 16:16, "Ralph Goers" <ra...@dslextreme.com> wrote:
Thanks, my mistake. Yes, please create a Jira. We should add something like %ex{short.exceptionName}.
Ralph
> On Aug 15, 2018, at 12:26 AM, Fröstl, Christian <ch...@accenture.com> wrote:
>
> Because this only includes the calling class name, and not the exception name.
>
> Example exception:
> de.test.test.UnknownIdentifierException: CronJob with code test not found
> at de.test.test.service.Services.validateSingleResultWithType(Services.java:88)
>
> results in:
> class name ($ex{short.className}) = de.test.test.service.Services
>
> but I like to have the thrown name:
> de.test.test.UnknownIdentifierException
>
> Greetings,
> Christian
>
> On 15.08.18, 01:55, "Ralph Goers" <ra...@dslextreme.com> wrote:
>
> Is there a reason why you cannot use $ex{short.className} in your pattern?
>
> Ralph
>
>> On Aug 14, 2018, at 2:21 PM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
>>
>> On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
>> christian.froestl@accenture.com> wrote:
>>
>>> To be more precise, I only need the name of the exception in a dedicated
>>> field like the thrown_name in the JSON layout.
>>>
>>> Greetings,
>>> Christian
>>>
>>> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
>>> wrote:
>>>
>>> We like to have a local log format and don't like to send all logs
>>> directly to the server.
>>> Do you have any idea to get this format in a patternlayout?
>>>
>>> Thanks and greetings,
>>> Christian
>>>
>>> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>>>
>>> Have you tried out the GELF layout?
>>>
>>> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
>>> christian.froestl@accenture.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> we are using the log4j2 json appender to generate json logs
>>> which will be
>>>> used in graylog.
>>>> The JSON layout doesn’t fit perfectly for us, and I tried to
>>> create our
>>>> own JSON by using the RollingRandomAccessFile appender with the
>>>> patternLayout and the JSON encoding function.
>>>> This fits very good for us, but I am not able to create a field
>>>> thrown_name, like in the JSON appender.
>>>>
>>>> Example of JSON Appender:
>>>> Field name: thrown_extendedStackTrace
>>>> Value: org.springframework.beans.FatalBeanException; .........
>>> <the whole
>>>> stacktrace>
>>>>
>>>> Field name: thrown_name
>>>> Value: org.springframework.beans.FatalBeanException
>>>>
>>>> It is no problem to generate the whole stacktrace in
>>> patternlayout using
>>>> this code snippet: enc{%throwable}{JSON}
>>>> But how to generate a field which only includes the thrown_name
>>> of the
>>>> exception?
>>>>
>>>> Thanks and greetings,
>>>> Christian
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> This message is for the designated recipient only and may contain
>>>> privileged, proprietary, or otherwise confidential information.
>>> If you have
>>>> received it in error, please notify the sender immediately and
>>> delete the
>>>> original. Any other use of the e-mail by you is prohibited.
>>> Where allowed
>>>> by local law, electronic communications with Accenture and its
>>> affiliates,
>>>> including e-mail and instant messaging (including content), may
>>> be scanned
>>>> by our systems for the purposes of information security and
>>> assessment of
>>>> internal compliance with Accenture policy. Your privacy is
>>> important to us.
>>>> Accenture uses your personal data only in compliance with data
>>> protection
>>>> laws. For further information on how Accenture processes your
>>> personal
>>>> data, please see our privacy statement at
>>>> https://www.accenture.com/us-en/privacy-policy.
>>>>
>>>>
>>> ______________________________________________________________________________________
>>>>
>>>> www.accenture.com
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> This message is for the designated recipient only and may contain
>>> privileged, proprietary, or otherwise confidential information. If you have
>>> received it in error, please notify the sender immediately and delete the
>>> original. Any other use of the e-mail by you is prohibited. Where allowed
>>> by local law, electronic communications with Accenture and its affiliates,
>>> including e-mail and instant messaging (including content), may be scanned
>>> by our systems for the purposes of information security and assessment of
>>> internal compliance with Accenture policy. Your privacy is important to us.
>>> Accenture uses your personal data only in compliance with data protection
>>> laws. For further information on how Accenture processes your personal
>>> data, please see our privacy statement at
>>> https://www.accenture.com/us-en/privacy-policy.
>>>
>>> ______________________________________________________________________________________
>>>
>>> www.accenture.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> www.accenture.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: [External] Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks, my mistake. Yes, please create a Jira. We should add something like %ex{short.exceptionName}.
Ralph
> On Aug 15, 2018, at 12:26 AM, Fröstl, Christian <ch...@accenture.com> wrote:
>
> Because this only includes the calling class name, and not the exception name.
>
> Example exception:
> de.test.test.UnknownIdentifierException: CronJob with code test not found
> at de.test.test.service.Services.validateSingleResultWithType(Services.java:88)
>
> results in:
> class name ($ex{short.className}) = de.test.test.service.Services
>
> but I like to have the thrown name:
> de.test.test.UnknownIdentifierException
>
> Greetings,
> Christian
>
> On 15.08.18, 01:55, "Ralph Goers" <ra...@dslextreme.com> wrote:
>
> Is there a reason why you cannot use $ex{short.className} in your pattern?
>
> Ralph
>
>> On Aug 14, 2018, at 2:21 PM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
>>
>> On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
>> christian.froestl@accenture.com> wrote:
>>
>>> To be more precise, I only need the name of the exception in a dedicated
>>> field like the thrown_name in the JSON layout.
>>>
>>> Greetings,
>>> Christian
>>>
>>> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
>>> wrote:
>>>
>>> We like to have a local log format and don't like to send all logs
>>> directly to the server.
>>> Do you have any idea to get this format in a patternlayout?
>>>
>>> Thanks and greetings,
>>> Christian
>>>
>>> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>>>
>>> Have you tried out the GELF layout?
>>>
>>> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
>>> christian.froestl@accenture.com> wrote:
>>>
>>>> Hi everybody,
>>>>
>>>> we are using the log4j2 json appender to generate json logs
>>> which will be
>>>> used in graylog.
>>>> The JSON layout doesn’t fit perfectly for us, and I tried to
>>> create our
>>>> own JSON by using the RollingRandomAccessFile appender with the
>>>> patternLayout and the JSON encoding function.
>>>> This fits very good for us, but I am not able to create a field
>>>> thrown_name, like in the JSON appender.
>>>>
>>>> Example of JSON Appender:
>>>> Field name: thrown_extendedStackTrace
>>>> Value: org.springframework.beans.FatalBeanException; .........
>>> <the whole
>>>> stacktrace>
>>>>
>>>> Field name: thrown_name
>>>> Value: org.springframework.beans.FatalBeanException
>>>>
>>>> It is no problem to generate the whole stacktrace in
>>> patternlayout using
>>>> this code snippet: enc{%throwable}{JSON}
>>>> But how to generate a field which only includes the thrown_name
>>> of the
>>>> exception?
>>>>
>>>> Thanks and greetings,
>>>> Christian
>>>>
>>>>
>>>>
>>>> ________________________________
>>>>
>>>> This message is for the designated recipient only and may contain
>>>> privileged, proprietary, or otherwise confidential information.
>>> If you have
>>>> received it in error, please notify the sender immediately and
>>> delete the
>>>> original. Any other use of the e-mail by you is prohibited.
>>> Where allowed
>>>> by local law, electronic communications with Accenture and its
>>> affiliates,
>>>> including e-mail and instant messaging (including content), may
>>> be scanned
>>>> by our systems for the purposes of information security and
>>> assessment of
>>>> internal compliance with Accenture policy. Your privacy is
>>> important to us.
>>>> Accenture uses your personal data only in compliance with data
>>> protection
>>>> laws. For further information on how Accenture processes your
>>> personal
>>>> data, please see our privacy statement at
>>>> https://www.accenture.com/us-en/privacy-policy.
>>>>
>>>>
>>> ______________________________________________________________________________________
>>>>
>>>> www.accenture.com
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>>
>>>
>>> ________________________________
>>>
>>> This message is for the designated recipient only and may contain
>>> privileged, proprietary, or otherwise confidential information. If you have
>>> received it in error, please notify the sender immediately and delete the
>>> original. Any other use of the e-mail by you is prohibited. Where allowed
>>> by local law, electronic communications with Accenture and its affiliates,
>>> including e-mail and instant messaging (including content), may be scanned
>>> by our systems for the purposes of information security and assessment of
>>> internal compliance with Accenture policy. Your privacy is important to us.
>>> Accenture uses your personal data only in compliance with data protection
>>> laws. For further information on how Accenture processes your personal
>>> data, please see our privacy statement at
>>> https://www.accenture.com/us-en/privacy-policy.
>>>
>>> ______________________________________________________________________________________
>>>
>>> www.accenture.com
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
> ______________________________________________________________________________________
>
> www.accenture.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: [External] Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Fröstl,
Christian <ch...@accenture.com>.
Because this only includes the calling class name, and not the exception name.
Example exception:
de.test.test.UnknownIdentifierException: CronJob with code test not found
at de.test.test.service.Services.validateSingleResultWithType(Services.java:88)
results in:
class name ($ex{short.className}) = de.test.test.service.Services
but I like to have the thrown name:
de.test.test.UnknownIdentifierException
Greetings,
Christian
On 15.08.18, 01:55, "Ralph Goers" <ra...@dslextreme.com> wrote:
Is there a reason why you cannot use $ex{short.className} in your pattern?
Ralph
> On Aug 14, 2018, at 2:21 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
>
> On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
> christian.froestl@accenture.com> wrote:
>
>> To be more precise, I only need the name of the exception in a dedicated
>> field like the thrown_name in the JSON layout.
>>
>> Greetings,
>> Christian
>>
>> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
>> wrote:
>>
>> We like to have a local log format and don't like to send all logs
>> directly to the server.
>> Do you have any idea to get this format in a patternlayout?
>>
>> Thanks and greetings,
>> Christian
>>
>> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>>
>> Have you tried out the GELF layout?
>>
>> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
>> christian.froestl@accenture.com> wrote:
>>
>>> Hi everybody,
>>>
>>> we are using the log4j2 json appender to generate json logs
>> which will be
>>> used in graylog.
>>> The JSON layout doesn’t fit perfectly for us, and I tried to
>> create our
>>> own JSON by using the RollingRandomAccessFile appender with the
>>> patternLayout and the JSON encoding function.
>>> This fits very good for us, but I am not able to create a field
>>> thrown_name, like in the JSON appender.
>>>
>>> Example of JSON Appender:
>>> Field name: thrown_extendedStackTrace
>>> Value: org.springframework.beans.FatalBeanException; .........
>> <the whole
>>> stacktrace>
>>>
>>> Field name: thrown_name
>>> Value: org.springframework.beans.FatalBeanException
>>>
>>> It is no problem to generate the whole stacktrace in
>> patternlayout using
>>> this code snippet: enc{%throwable}{JSON}
>>> But how to generate a field which only includes the thrown_name
>> of the
>>> exception?
>>>
>>> Thanks and greetings,
>>> Christian
>>>
>>>
>>>
>>> ________________________________
>>>
>>> This message is for the designated recipient only and may contain
>>> privileged, proprietary, or otherwise confidential information.
>> If you have
>>> received it in error, please notify the sender immediately and
>> delete the
>>> original. Any other use of the e-mail by you is prohibited.
>> Where allowed
>>> by local law, electronic communications with Accenture and its
>> affiliates,
>>> including e-mail and instant messaging (including content), may
>> be scanned
>>> by our systems for the purposes of information security and
>> assessment of
>>> internal compliance with Accenture policy. Your privacy is
>> important to us.
>>> Accenture uses your personal data only in compliance with data
>> protection
>>> laws. For further information on how Accenture processes your
>> personal
>>> data, please see our privacy statement at
>>> https://www.accenture.com/us-en/privacy-policy.
>>>
>>>
>> ______________________________________________________________________________________
>>>
>>> www.accenture.com
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you have
>> received it in error, please notify the sender immediately and delete the
>> original. Any other use of the e-mail by you is prohibited. Where allowed
>> by local law, electronic communications with Accenture and its affiliates,
>> including e-mail and instant messaging (including content), may be scanned
>> by our systems for the purposes of information security and assessment of
>> internal compliance with Accenture policy. Your privacy is important to us.
>> Accenture uses your personal data only in compliance with data protection
>> laws. For further information on how Accenture processes your personal
>> data, please see our privacy statement at
>> https://www.accenture.com/us-en/privacy-policy.
>>
>> ______________________________________________________________________________________
>>
>> www.accenture.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
Re: [External] Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Ralph Goers <ra...@dslextreme.com>.
Is there a reason why you cannot use $ex{short.className} in your pattern?
Ralph
> On Aug 14, 2018, at 2:21 PM, Matt Sicker <bo...@gmail.com> wrote:
>
> Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
>
> On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
> christian.froestl@accenture.com> wrote:
>
>> To be more precise, I only need the name of the exception in a dedicated
>> field like the thrown_name in the JSON layout.
>>
>> Greetings,
>> Christian
>>
>> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
>> wrote:
>>
>> We like to have a local log format and don't like to send all logs
>> directly to the server.
>> Do you have any idea to get this format in a patternlayout?
>>
>> Thanks and greetings,
>> Christian
>>
>> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>>
>> Have you tried out the GELF layout?
>>
>> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
>> christian.froestl@accenture.com> wrote:
>>
>>> Hi everybody,
>>>
>>> we are using the log4j2 json appender to generate json logs
>> which will be
>>> used in graylog.
>>> The JSON layout doesn’t fit perfectly for us, and I tried to
>> create our
>>> own JSON by using the RollingRandomAccessFile appender with the
>>> patternLayout and the JSON encoding function.
>>> This fits very good for us, but I am not able to create a field
>>> thrown_name, like in the JSON appender.
>>>
>>> Example of JSON Appender:
>>> Field name: thrown_extendedStackTrace
>>> Value: org.springframework.beans.FatalBeanException; .........
>> <the whole
>>> stacktrace>
>>>
>>> Field name: thrown_name
>>> Value: org.springframework.beans.FatalBeanException
>>>
>>> It is no problem to generate the whole stacktrace in
>> patternlayout using
>>> this code snippet: enc{%throwable}{JSON}
>>> But how to generate a field which only includes the thrown_name
>> of the
>>> exception?
>>>
>>> Thanks and greetings,
>>> Christian
>>>
>>>
>>>
>>> ________________________________
>>>
>>> This message is for the designated recipient only and may contain
>>> privileged, proprietary, or otherwise confidential information.
>> If you have
>>> received it in error, please notify the sender immediately and
>> delete the
>>> original. Any other use of the e-mail by you is prohibited.
>> Where allowed
>>> by local law, electronic communications with Accenture and its
>> affiliates,
>>> including e-mail and instant messaging (including content), may
>> be scanned
>>> by our systems for the purposes of information security and
>> assessment of
>>> internal compliance with Accenture policy. Your privacy is
>> important to us.
>>> Accenture uses your personal data only in compliance with data
>> protection
>>> laws. For further information on how Accenture processes your
>> personal
>>> data, please see our privacy statement at
>>> https://www.accenture.com/us-en/privacy-policy.
>>>
>>>
>> ______________________________________________________________________________________
>>>
>>> www.accenture.com
>>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>>
>>
>> ________________________________
>>
>> This message is for the designated recipient only and may contain
>> privileged, proprietary, or otherwise confidential information. If you have
>> received it in error, please notify the sender immediately and delete the
>> original. Any other use of the e-mail by you is prohibited. Where allowed
>> by local law, electronic communications with Accenture and its affiliates,
>> including e-mail and instant messaging (including content), may be scanned
>> by our systems for the purposes of information security and assessment of
>> internal compliance with Accenture policy. Your privacy is important to us.
>> Accenture uses your personal data only in compliance with data protection
>> laws. For further information on how Accenture processes your personal
>> data, please see our privacy statement at
>> https://www.accenture.com/us-en/privacy-policy.
>>
>> ______________________________________________________________________________________
>>
>> www.accenture.com
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-user-help@logging.apache.org
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: [External] Re: Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Matt Sicker <bo...@gmail.com>.
Sounds like a new feature then. Please file a JIRA ticket. PRs welcome!
On Tue, 14 Aug 2018 at 01:53, Fröstl, Christian <
christian.froestl@accenture.com> wrote:
> To be more precise, I only need the name of the exception in a dedicated
> field like the thrown_name in the JSON layout.
>
> Greetings,
> Christian
>
> On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com>
> wrote:
>
> We like to have a local log format and don't like to send all logs
> directly to the server.
> Do you have any idea to get this format in a patternlayout?
>
> Thanks and greetings,
> Christian
>
> On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
>
> Have you tried out the GELF layout?
>
> On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
> christian.froestl@accenture.com> wrote:
>
> > Hi everybody,
> >
> > we are using the log4j2 json appender to generate json logs
> which will be
> > used in graylog.
> > The JSON layout doesn’t fit perfectly for us, and I tried to
> create our
> > own JSON by using the RollingRandomAccessFile appender with the
> > patternLayout and the JSON encoding function.
> > This fits very good for us, but I am not able to create a field
> > thrown_name, like in the JSON appender.
> >
> > Example of JSON Appender:
> > Field name: thrown_extendedStackTrace
> > Value: org.springframework.beans.FatalBeanException; .........
> <the whole
> > stacktrace>
> >
> > Field name: thrown_name
> > Value: org.springframework.beans.FatalBeanException
> >
> > It is no problem to generate the whole stacktrace in
> patternlayout using
> > this code snippet: enc{%throwable}{JSON}
> > But how to generate a field which only includes the thrown_name
> of the
> > exception?
> >
> > Thanks and greetings,
> > Christian
> >
> >
> >
> > ________________________________
> >
> > This message is for the designated recipient only and may contain
> > privileged, proprietary, or otherwise confidential information.
> If you have
> > received it in error, please notify the sender immediately and
> delete the
> > original. Any other use of the e-mail by you is prohibited.
> Where allowed
> > by local law, electronic communications with Accenture and its
> affiliates,
> > including e-mail and instant messaging (including content), may
> be scanned
> > by our systems for the purposes of information security and
> assessment of
> > internal compliance with Accenture policy. Your privacy is
> important to us.
> > Accenture uses your personal data only in compliance with data
> protection
> > laws. For further information on how Accenture processes your
> personal
> > data, please see our privacy statement at
> > https://www.accenture.com/us-en/privacy-policy.
> >
> >
> ______________________________________________________________________________________
> >
> > www.accenture.com
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
>
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-user-help@logging.apache.org
>
--
Matt Sicker <bo...@gmail.com>
Re: [External] Re: Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Fröstl,
Christian <ch...@accenture.com>.
To be more precise, I only need the name of the exception in a dedicated field like the thrown_name in the JSON layout.
Greetings,
Christian
On 14.08.18, 08:36, "Fröstl, Christian" <ch...@accenture.com> wrote:
We like to have a local log format and don't like to send all logs directly to the server.
Do you have any idea to get this format in a patternlayout?
Thanks and greetings,
Christian
On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
Have you tried out the GELF layout?
On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
christian.froestl@accenture.com> wrote:
> Hi everybody,
>
> we are using the log4j2 json appender to generate json logs which will be
> used in graylog.
> The JSON layout doesn’t fit perfectly for us, and I tried to create our
> own JSON by using the RollingRandomAccessFile appender with the
> patternLayout and the JSON encoding function.
> This fits very good for us, but I am not able to create a field
> thrown_name, like in the JSON appender.
>
> Example of JSON Appender:
> Field name: thrown_extendedStackTrace
> Value: org.springframework.beans.FatalBeanException; ......... <the whole
> stacktrace>
>
> Field name: thrown_name
> Value: org.springframework.beans.FatalBeanException
>
> It is no problem to generate the whole stacktrace in patternlayout using
> this code snippet: enc{%throwable}{JSON}
> But how to generate a field which only includes the thrown_name of the
> exception?
>
> Thanks and greetings,
> Christian
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
--
Matt Sicker <bo...@gmail.com>
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: [External] Re: Get thrown_name from JSON appender in
RollingRandomAccessFile appender
Posted by Fröstl,
Christian <ch...@accenture.com>.
We like to have a local log format and don't like to send all logs directly to the server.
Do you have any idea to get this format in a patternlayout?
Thanks and greetings,
Christian
On 13.08.18, 20:53, "Matt Sicker" <bo...@gmail.com> wrote:
Have you tried out the GELF layout?
On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
christian.froestl@accenture.com> wrote:
> Hi everybody,
>
> we are using the log4j2 json appender to generate json logs which will be
> used in graylog.
> The JSON layout doesn’t fit perfectly for us, and I tried to create our
> own JSON by using the RollingRandomAccessFile appender with the
> patternLayout and the JSON encoding function.
> This fits very good for us, but I am not able to create a field
> thrown_name, like in the JSON appender.
>
> Example of JSON Appender:
> Field name: thrown_extendedStackTrace
> Value: org.springframework.beans.FatalBeanException; ......... <the whole
> stacktrace>
>
> Field name: thrown_name
> Value: org.springframework.beans.FatalBeanException
>
> It is no problem to generate the whole stacktrace in patternlayout using
> this code snippet: enc{%throwable}{JSON}
> But how to generate a field which only includes the thrown_name of the
> exception?
>
> Thanks and greetings,
> Christian
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
--
Matt Sicker <bo...@gmail.com>
________________________________
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.
______________________________________________________________________________________
www.accenture.com
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-user-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-user-help@logging.apache.org
Re: Get thrown_name from JSON appender in RollingRandomAccessFile appender
Posted by Matt Sicker <bo...@gmail.com>.
Have you tried out the GELF layout?
On Mon, 13 Aug 2018 at 11:09, Fröstl, Christian <
christian.froestl@accenture.com> wrote:
> Hi everybody,
>
> we are using the log4j2 json appender to generate json logs which will be
> used in graylog.
> The JSON layout doesn’t fit perfectly for us, and I tried to create our
> own JSON by using the RollingRandomAccessFile appender with the
> patternLayout and the JSON encoding function.
> This fits very good for us, but I am not able to create a field
> thrown_name, like in the JSON appender.
>
> Example of JSON Appender:
> Field name: thrown_extendedStackTrace
> Value: org.springframework.beans.FatalBeanException; ......... <the whole
> stacktrace>
>
> Field name: thrown_name
> Value: org.springframework.beans.FatalBeanException
>
> It is no problem to generate the whole stacktrace in patternlayout using
> this code snippet: enc{%throwable}{JSON}
> But how to generate a field which only includes the thrown_name of the
> exception?
>
> Thanks and greetings,
> Christian
>
>
>
> ________________________________
>
> This message is for the designated recipient only and may contain
> privileged, proprietary, or otherwise confidential information. If you have
> received it in error, please notify the sender immediately and delete the
> original. Any other use of the e-mail by you is prohibited. Where allowed
> by local law, electronic communications with Accenture and its affiliates,
> including e-mail and instant messaging (including content), may be scanned
> by our systems for the purposes of information security and assessment of
> internal compliance with Accenture policy. Your privacy is important to us.
> Accenture uses your personal data only in compliance with data protection
> laws. For further information on how Accenture processes your personal
> data, please see our privacy statement at
> https://www.accenture.com/us-en/privacy-policy.
>
> ______________________________________________________________________________________
>
> www.accenture.com
>
--
Matt Sicker <bo...@gmail.com>