I know that a great deal of care has been put into making slf4j invisible to the application doing the logging.  This includes configuration errors being transparent and all.

We consider logging framework configuration errors fatal, and would like a mechanism that can tell the main application that the logging framework is broken so it can do an emergency shutdown.      Our usecase is at application start up (first logging statement) but the generic case would probably be after each (re)configuration.

As we by default cannot specify this through the configuration file, this probably needs to be triggered by a system property.  I'd really prefer a solution which does not "know in application code" that the slf4j backend is logback.