Extended Stacktrace in Kibana is missing although logger is passing Throwable

[mwoelm]

Hi,

In our code we following lines where I want to analyze an error:

try {
    return convertPageData(orderResults, getOrderHistoryConverter());
} catch (Exception e) {
    LOG.error("Couldn't convert Page Data.", e);

In Kibana, I can see that the exception is thrown. The Logger is based on SLF4J Logger. By passing the exception, I should be able to see the extended Stacktrace in Kibana, shouldn't I?

Sadly, I don't. I just see:

{"instant":{"epochSecond":1656070029,"nanoOfSecond":926315000},"thread":"hybrisHTTP33","level":"ERROR","loggerName":"...","message":"Couldn't convert Page Data.","thrown":{"commonElementCount":0,"name":"java.lang.NullPointerException"},"endOfBatch":false,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger","contextMap":{"RemoteAddr":"[46.243.120.67] ","Tenant":""},"threadId":162,"threadPriority":5,"origin":"PLATFORM"}

How can I LOG an error to see the full stacktrace in Kibana?

Best Regards,

Michael

[samuelyang]

Hi Michael,

In my standard environment, I can see the full stacktrace.

You should also be able to see the full stacktrace in Kibana, otherwise please raise a support ticket.