Thread: [log4perl-devel] Custom Level/Priority

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

Hi,

Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
for my program?

Regards,

Anthony

On Wed, 4 Jan 2006, Anthony Chee wrote:

> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?

Sure, check out the "custom log levels" of the main manual page:

    http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb

-- Mike

Mike Schilli
m...@pe...

Thanks for help.

It mentioned create_custom_level can be put in configuration file. I would
like to know what's the syntax?

Is it something like

Log4perl.Logger.create_custom_level() = WARN ?

Regards,
Anthony

-----Original Message-----
From: Mike Schilli [mailto:m...@pe...] 
Sent: Wednesday, January 04, 2006 12:28 PM
To: Anthony Chee
Cc: log...@li...
Subject: Re: [log4perl-devel] Custom Level/Priority

On Wed, 4 Jan 2006, Anthony Chee wrote:

> Besides INFO, DEBUG, ...... built-in level, can I build custom level OTHER
> for my program?

Sure, check out the "custom log levels" of the main manual page:

    http://log4perl.sourceforge.net/d/Log/Log4perl.html#d21fb

-- Mike

Mike Schilli
m...@pe...

On Wed, 4 Jan 2006, Anthony Chee wrote:

> It mentioned create_custom_level can be put in configuration file. I would
> like to know what's the syntax?

It says that "These levels can also be *used* in your config file", which means
you define them (in Perl) before you call Log::Log4perl::init(...) in
your code. Levels defined before init() can then used in the config file.

-- Mike

Mike Schilli
m...@pe...

Anthony Chee wrote:

> Hi,
>
> Besides INFO, DEBUG, ...... built-in level, can I build custom level 
> OTHER for my program?
>
> Regards,
>
> Anthony
>

This *isnt* to say youre *wrong*, but Id point you to some guidance in 
the docs.

from perldoc Log::Log4perl, section Log Levels

But nobody does that, really. Neither does anyone need more logging 
levels than these predefined
ones. If you think you do, I would suggest you look into steering your 
logging behaviour via the
category mechanism.

If you need to find out if the currently configured logging level would 
allow a logger’s logging
statement to go through, use the logger’s "is_level()" methods:

'OTHER' seems both reasonable, and a cop-out, both at the same time.

Youve got *the-man* answering questions, I'll wager that if you
speak to your particular circumstance, and why you chose the OTHER way 
(pun intended),
he can respond to the tradeoffs in your case.