Bug #75781 for Log-Log4perl: make $logger->error_die available in :easy mode or tune down LOGDIE/CROAK/EXIT to ERROR

Thu Mar 15 05:34:39 2012 joerg.meltzer [...] tngtech.com - Ticket created

Subject:

make $logger->error_die available in :easy mode or tune down LOGDIE/CROAK/EXIT to ERROR

I am using Log::Log4perl with a Syslog appender in :easy mode. Currently I am flooded with Syslog messages whenever I LOGDIE LOGCROAK LOGEXIT in a script, as all of them log on FATAL severity. It would be nice to either tune the Loglevel down to ERROR or provide an ERRORDIE subroutine.

Fri Mar 16 03:21:09 2012 MSCHILLI [...] cpan.org - Correspondence added

Show quoted text

> Currently I am flooded with Syslog messages whenever I LOGDIE LOGCROAK > LOGEXIT in a script, as all of them log on FATAL severity.

Throwing LOGDIE and exiting an application because it makes no sense to keep it running is a pretty severe condition, though, which I would expect to be reflected in a FATAL message in syslog. I'm no expert in syslog levels, so help me out here: Isn't FATAL exactly the definition of an application unable to continue because of a severe condition?

Fri Mar 16 03:21:10 2012 The RT System itself - Status changed from 'new' to 'open'

Fri Mar 16 04:24:53 2012 joerg.meltzer [...] tngtech.com - Correspondence added

From:

joerg.meltzer [...] tngtech.com

Am Fr 16. Mär 2012, 03:21:09, MSCHILLI schrieb: Show quoted text

> > Currently I am flooded with Syslog messages whenever I LOGDIE LOGCROAK > > LOGEXIT in a script, as all of them log on FATAL severity.

> > Throwing LOGDIE and exiting an application because it makes no sense to > keep it running is a pretty severe condition, though, which I would > expect to be reflected in a FATAL message in syslog. > > I'm no expert in syslog levels, so help me out here: Isn't FATAL exactly > the definition of an application unable to continue because of a severe > condition?

I think FATAL is a reasonable default for LOGDIE, however to me the severity of a die isn't always the same. It makes a difference, whether I run a mission critical daemon (then it should be FATAL) or just a bunch of interactive scripts. To give my case a bit of context. I want to provision virtual machines, which is interactive, but I also want it to be logged so logging data can be used for monitoring. I want to have a monitoring tool decide what is fatal.

Tue Mar 20 02:12:21 2012 MSCHILLI [...] cpan.org - Correspondence added

On Fri Mar 16 04:24:53 2012, codeacrobat wrote: Show quoted text

> It makes a difference, whether I run a mission critical daemon (then it > should be FATAL) or just a bunch of interactive scripts.

Hmm, not sure if this is an generally applicable law, but how about you use Log::Log4perl->get_logger->error_die("Whoa!"); in these cases?

Tue Mar 20 02:53:09 2012 joerg.meltzer [...] tngtech.com - Correspondence added

From:

joerg.meltzer [...] tngtech.com

Am Di 20. Mär 2012, 02:12:21, MSCHILLI schrieb: Show quoted text

> Hmm, not sure if this is an generally applicable law, but how about

you use Show quoted text

> > Log::Log4perl->get_logger->error_die("Whoa!"); > > in these cases?

That would totally defeat the easy mode we are using so far. It is hard enough to convince some colleagues to use a perl script rather then logging something with /bin/echo in some clunky shell script. The clean code pope solution probably would involve setting exceptions to the send "wall" notifications on emerg level in the syslog configuration and using a complicated Syslog appender script config. If this is even possible, it is not something you find easily in the manual. (If you do please put it in the FAQ.) Therefore I suggest to have an ERRORDIE in easy mode.

Tue Mar 20 03:17:29 2012 joerg.meltzer [...] tngtech.com - Correspondence added

From:

joerg.meltzer [...] tngtech.com

FYI, there is a SOPW question at perlmonks.org on this issue. http://perlmonks.org/?node_id=960540 Regards, codeacrobat Am Di 20. Mär 2012, 02:53:09, codeacrobat schrieb: Show quoted text

> Am Di 20. Mär 2012, 02:12:21, MSCHILLI schrieb:

> > Hmm, not sure if this is an generally applicable law, but how about

> you use

> > > > Log::Log4perl->get_logger->error_die("Whoa!"); > > > > in these cases?

> > That would totally defeat the easy mode we are using so far. > It is hard enough to convince some colleagues to use a perl script > rather then logging something with /bin/echo in some clunky shell script. > > > The clean code pope solution probably would involve setting exceptions > to the send "wall" notifications on emerg level in the syslog > configuration and using a complicated Syslog appender script config. > > If this is even possible, it is not something you find easily in the > manual. (If you do please put it in the FAQ.) > > Therefore I suggest to have an ERRORDIE in easy mode.