POE::Co...og4perl(3)

πŸ“¦
version 0.03 Β· 2 versions
, in fedora 43

πŸ’– POE::Component::Log4perl πŸ’–

okay bestie, so this is POE::Component::Log4perl(3) β€” a User Contributed Perl Documentation page, and honestly? it's giving "logging, but make it POE." 🌸


✨ NAME ✨

POE::Component::Log4perl β€” a Perl extension for the POE Environemt

yes, "Environemt." that's the original spelling, and I am not fixing it. character development πŸ’…

πŸŽ€ SYNOPSIS πŸŽ€

  use POE::Component::Log4perl;

  POE::Component::Log4perl->spawn(
     Alias => 'logger',
     Category => 'default',
     ConfigFile => 'logging.conf',
     GetLogfile => \&get_logfile,
  );

look at that. four little params and you're logging like a main character. πŸ¦‹


🌈 DESCRIPTION 🌈

Well, just what everybody needs, another logging module for the POE environment. This one will encapsulate the Log4perl modules to do the logging.

This modules understands the following parameters:

  • Alias β€” The alias for the session
  • Category β€” The category to use from the configuration file
  • ConfigFile β€” The name of the configuration file
  • GetLogfile β€” This points to a function to return the logfile name

okay so a word about the GetLogfile parameter, because it's lowkey the whole personality of this module. In my environment, I use a single centralized configuration file to handle the logging environment. This makes management a bit easier. Log4perl allows this to happen by using a callback to your main routine to retrieve the filename. The GetLogfile allows you to name the function to handle that task. The function name should match the one in the configuration file. If you don't use this ability then you can safely ignore this parameter. fr fr, it's optional, no pressure. 🫢


⭐ EVENTS ⭐

info

This event will insert an "INFO" line into your logfile.

Example:

     $poe_kernel->post('logger' => info => 'my cool message');

warn

This event will insert a "WARN" line into your logfile.

error

This event will insert an "ERROR" line into your logfile.

fatal

This event will insert a "FATAL" line into your logfile.

Example:

     $poe_kernel->post('logger' => fatal => 'bad mojo');
     $poe_kernel->yield('shutdown');
πŸ’€ "bad mojo" then immediately shutting down. iconic. that's the whole mood.

debug

This event will insert a "DEBUG" line into your logfile.


πŸ”₯ SEE ALSO πŸ”₯

  • Log::Log4perl
  • POE::Component::Logger
  • POE::Component::SimpleLogger

the little log4perl family reunion, we love to see it πŸ’œ


πŸ‘‘ AUTHOR πŸ‘‘

Kevin L. Esteb, <kesteb@wsipc.org>


Copyright (C) 2007 by Kevin L. Esteb

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.8 or, at your option, any later version of Perl 5 you may have available.


and that's the whole page bestie, no cap. this one's from perl v5.42.0, dated 2025-07-25, and it's POE::Co...og4perl(3) β€” the manual page that got its title cut off but never its vibes. go forth and log. βœ¨πŸ’–βœ¨

πŸ“¦ where this page comes from