[slf4j-dev] FATAL level

[Ceki Gulcu]

Hello Lilianne,

Sorry for not replying earlier.

I don't believe there is strong demand for this level. Moreover, each
level requires ten new methods to be added to the Logger interface
which in turn need to be implemented in each binding which I am not
too keen on doing.

If you were using logback-classic, you could highlight the
"fatality" of a log by coloring it with a marker named FATAL or
similar.

HTH,

Lilianne E. Blaze wrote:
> Is anyone reading this?
> 
> L
> 
> Lilianne E. Blaze wrote:
>> Hello,
>> Could you please reconsider adding FATAL level?
>> I read and understand the argument at
>> http://www.slf4j.org/faq.html#fatal , but actually there are scenarios
>> where the two levels are different - for example, inconsistencies in a
>> database might be classified as ERROR, but failing hardware or
>> inconsistencies suggesting unauthorized access are need immediate
>> attention are FATAL.
>> Application saying "I'm out of memory, I'm quitting in hope that os will
>> restart me soon as defined in cron" is error.
>> Same application saying "I think I'm being hacked now, help me" is fatal.
>> Also, it's reasonable to configure logging system to forward error
>> situations to admin's mail, and fatal ones to admin's cell phone.
>>
>> Greetings, Lilianne E. Blaze


-- 
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch