[logback-user] Making logging failures fatal.

ceki ceki at qos.ch
Mon Aug 13 18:25:01 CEST 2012

Hi Thorbjørn,

Have you considered writing a custom status listener [1]?

[1] http://logback.qos.ch/manual/configuration.html#statusListener

On 09.08.2012 13:43, Thorbjørn Ravn Andersen wrote:
> I need to make logback report problems back as exceptions.
> Our general deployment scenario is one where programs are restarted
> every day, and are tedious to monitor unless they explicitly make
> themselves heard.  Hence logfiles are important and a failure in the
> logging framework configuration should cause the program to stop there
> and then.
> To my knowledge things like “cannot write to log file X/Y/Z” or “bad
> configuration” are currently just logged using logbacks internal
> mechanism and the application does not know anything about it.
> I’d prefer not having logback specific code in my application as we
> strive to be logging framework neutral, but if it is unavoidable to do
> this I can make an exception.
> Thanks for any help
> /Thorbjørn

More information about the Logback-user mailing list