Open johnedo1234 opened 9 years ago
Looks like the impl is doing it's own writing of the stacktrace, and it leaves out all sorts of important info.
Seems simpler to just log the regular old Java stacktrace and leave it to the JDK to define what exactly that means.
Submitted pull request with fix: https://github.com/SYNAXON/logstash-util-formatter/pull/12
stacktrace field now includes the standard Java stacktrace in all its glory, even if the stacktrace is empty. KISS.
Causes and suppressed exceptions are absolutely critical to log.