Provide a Layout to StatusLogger

[voddan]

Is it possible to provide a layout to the status logger?

When I get networking problems with my appender, it prints elaborate error messages with extensive stack traces, even though a simple "Unable to connect to TCP:127.0.0.1:1234560" would be enough.

Is there a way to specify something like a PatternLayout for status logger, so that I could cut out the stack traces with a pattern "%m %eEx{0} %n"?
Did you find a work around for this issue?

[vy]

No, it is not possible and, IMHO, this is a good thing. Status Logger is the logger for the logger – that is, we need to keep its feature set at minimum. Consider it like a printf() on steroids.

When I get networking problems with my appender, it prints elaborate error messages with extensive stack traces

If this is an unexpected failure, it is good to point to the user the origin by means of a stack trace. If this is something regular, you might consider either introducing a rate limiter to the error messages you emit, or avoiding passing the same exception to the status logger in subsequent calls.

[voddan]

I see. That kinda makes sense, however I wish there was a way to at least turn of the stack traces. The error messages are somewhat useful to me as a user, but stack traces from inside of log4j are only useful for maintainers of the log4j library.

avoiding passing the same exception to the status logger in subsequent calls

Not applicable to me since my code is not using the status logger directly.

[ppkarwasz]

The error messages are somewhat useful to me as a user, but stack traces from inside of log4j are only useful for maintainers of the log4j library.

There are options for the date format of status logger, so I wouldn't be against an option that disables stack traces. Feel free to submit a PR.