Replies: 2 comments
-
@cpholt Thank you for the encouraging feedback. Please create a jira issue at jira.qos.ch asking for this issue to be fixed. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Ceki,
I see this resolved in the upcoming 1.3.9 release. Is there a planned date
for that? I can build a 1.3.9-SNAPSHOT version and incorporate that, but
just curious on when the official 1.3.9 might be published.
Thanks again for such a great piece of work!
…On Wed, Jun 21, 2023 at 4:30 AM Ceki Gülcü ***@***.***> wrote:
@cpholt <https://github.com/cpholt> Thank you for the encouraging
feedback.
Please create a jira issue at jira.qos.ch asking for this issue to be
fixed.
—
Reply to this email directly, view it on GitHub
<#673 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJ7YYV75QHAFWZRMUV2HDBTXMK5LFANCNFSM6AAAAAAZNNQNZY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
LOGBACK-1734 is great!! Thank you!! It connects logback output very easily now to fluentbit.
Can the Throwable's cause(s) be added to the structured JSON logging that was just added in LOGBACK-1734? I think it would be relatively easy to implement in ch.qos.logback.classic.encoder.JsonEncoder. Perhaps add a "cause" member to the "throwable" item, where the cause can also itself have a cause?
Beta Was this translation helpful? Give feedback.
All reactions