I am running into a similar issue as this post, where we have a wrapping logger that uses the current class name for context and delegates to Log4j.
The problem we are running into is many events triggered by this logger are being grouped together, because many of them have a single message and the stack trace is a single line indicating the message is coming from the wrapping logger. An example that may come through:
{User: admin, id: not specified, type: not specified} This is an example error message.
at com.hannonhill.cascade.util.logging.CascadeLogger.error(CascadeLogger.java:433)
Is there a recommended way to handle this setup so these events don’t get grouped together?
Thanks!