[logback-user] Best practices for FATAL errors...

[Chris Pratt]

An error, is an error.  The difference is what you do about it, not what
level it's logged at.
  (*Chris*)

On Sun, Aug 14, 2011 at 5:55 PM, Jason Berk <jasonrberk at gmail.com> wrote:

> +1
>
> I have the exact same question
>
> Sent from my iPhone
>
> On Aug 14, 2011, at 7:14 PM, Leon Rosenberg <rosenberg.leon at gmail.com>
> wrote:
>
> > Hi,
> >
> > since logback doesn't support log level FATAL I'm wondering how you
> > guys are separating between 'normal' errors and 'really bad' errors.
> > Example:
> > Warning: tried to insert statement into db, found key conflict,
> > resolved it (somehow).
> > Normal errors: couldn't insert the statement into db because the
> > encoding is invalid (or couldn't read user's file because its corrupt)
> > - affects one user.
> > Really bad errors: have no connection to db, so my further existence
> > is rather meaningless.
> >
> > So how do you guys log fatal errors without fatal? .-)
> >
> > best regards
> > Leon
> > _______________________________________________
> > Logback-user mailing list
> > Logback-user at qos.ch
> > http://qos.ch/mailman/listinfo/logback-user
> _______________________________________________
> Logback-user mailing list
> Logback-user at qos.ch
> http://qos.ch/mailman/listinfo/logback-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://qos.ch/pipermail/logback-user/attachments/20110814/55159f16/attachment.html>