first of all - thanks for your reply ...

but i thought, there is a more elegant solution included in log4perl .... hmmm ... it seams that i have to write a own appender for collecting and buffering the messages till i send it at the end of the script.

the point is that i do NOT want to write to disk and do NOT pass a message-string through all used modules (concatenating all messages).

Hi,

have a look at Log::Log4perl::Appender::String. I used it once for a similar reason.

But afterwards I don't think that the resulting code was nice. I think this is the wrong solution/architecture.

Best regards
McA

Hi McA

... it seams that this is what i searched for ;-) - Thanks! And i share your opinion about the architecture!

But if i use this Appender and fetch a appropriate logger of it ... how can i make my Moose Objects aware of this logger?

e.g. if i use the ROOT-logger i can do this with the Role Concept of Moose like this:

package My::Class;
use Moose;
with 'MooseX::Log::Log4perl';
...
$self->log->info("CREATED Object: " . $self->name);
[download]

But if i create my OWN-logger in my perl-script like this:

# my perl-script using My::Class
my $fileLogger = Log::Log4perl->get_logger('file');
[download]

i would have to pass the reference $fileLogger through ALL my Modules - have i? - or is there a better solution to make my Modules aware of $fileLogger??? (similar to the solution with ROOT-Logger)

Hi,

this is now more a MooseX::Log::Log4perl related question. When you look at the perldoc of that package IMHO anything is said. You have to initialize the Log::Log4perl singleton before logging the first time. Example is given in the perldoc.

Init like

my $log4perl_conf = q(
log4perl.logger=DEBUG, STRINGCOLLECTOR
log4perl.appender.STRINGCOLLECTOR = Log::Log4perl::Appender::String
log4perl.appender.STRINGCOLLECTOR.layout = Log::Log4perl::Layout::Patt
+ernLayout
log4perl.appender.STRINGCOLLECTOR.layout.ConversionPattern = %p:%d{ISO
+8601}:myscript: %m%n
);
Log::Log4perl->init( \$log4perl_conf );
[download]

before first usage.

UPDATE: As the doc says: You can get the logger instance with $self->logger. So later you should get the collected output with

my $appender = $self->logger->appender_by_name('STRINGCOLLECTOR');
my $string = '';
if($appender) {
    $string = $appender->string();
}
[download]

McA

http://search.cpan.org/perldoc/Log::Log4perl::FAQ#How_can_I_configure_Log::Log4perl_to_send_me_email_if_something_happens?
log4perl.appender.Mailer = Log::Dispatch::Email::MailSend
log4perl.appender.Mailer.to = drone@example.net
log4perl.appender.Mailer.subject = Something's broken!
log4perl.appender.Mailer.layout = SimpleLayout

Its unclear from the documentation when the email is sent, but its not immediately

hi

thanks for your reply, but i want to determine exactly when to send the mail. I know that your solution is buffering the logs before sending. Your can disable buffering with:

log4perl.appender.Mailer.buffered = 0
[download]

in your log4perl.conf

but this is not what i´m searching for ... nevertheless THANKS