On Tue, 13 May 2008, Erskine, Thomas (IT) wrote:
> While warp_message is indeed an appender setting, if you have two
> appenders, one with warp_message=0 and one without, then you'll get
> the mess I got: the one with will work fine and will have access to
> extra args separately, but the one with
Hi Mike.
While warp_message is indeed an appender setting, if you have two
appenders, one with warp_message=0 and one without, then you'll get the
mess I got: the one with will work fine and will have access to extra
args separately, but the one without will mash the args into a single
message.
On Tue, 13 May 2008, Erskine, Thomas (IT) wrote:
> I do indeed want
>
> $logger->log($level, $msg, $key)
>
> to be dealt with differently depending on the appender it ends up on.
> That's part of the point of having different appenders; they ought to be
> independant. The problem is that it
On Fri, 9 May 2008, Erskine, Thomas (IT) wrote:
> The other logs an event to Netcool (specifying warp_message=0) and it
> works fine. It allows you to call log like:
>
> $logger->log($level, $msg, $key)
>
> so that you can specify a Netcool alert key.
>
> Then comes the problem: I made a conf
(forwarded with permission)
Hi Mike.
I've been enjoying Log::Log4perl (using 1.13). Thank-you. Until I
decided to write a pair of appenders.
One of them is a fancy file appender and it works nicely.
The other logs an event to Netcool (specifying warp_message=0) and it
works fine. It allows y
