Object:...::Logger(3)

💅 Object::Remote::Logging::Logger — the glow-up page

okay so real talk, bestie: this is a page from the User Contributed Perl Documentation set, and it's all about Object::Remote::Logging::Logger — the class that formats your log messages and yeets them out to the world. Let's get into it ✨

---

🎀 NAME

Object::Remote::Logging::Logger — literally formats a log message and outputs it. That's the whole job. Iconic behavior honestly.

---

✨ SYNOPSIS

okay so here's the vibe in code form, copying exactly so you don't have to squint:

use Object::Remote::Logging::Logger;
use Object::Remote::Logging qw( router arg_levels );

my $app_output = Object::Remote::Logging::Logger->new(
  level_names => arg_levels, format => '%t %s',
  min_level => 'verbose', max_level => 'info',
);

#Selector method can return 0 or more logger
#objects that will receive the messages
my $selector = sub {
  my ($generating_package, $metadata) = @_;
  return unless $metadata->{exporter} eq 'App::Logging::Subclass';
  return $app_output;
};

#true value as second argument causes the selector
#to be stored with a weak reference
router->connect($selector, 1);

#disconnect the selector from the router
undef($selector);

#router will hold this logger forever
#and send it all log messages
router->connect(Object::Remote::Logging::Logger->new(
  level_names => arg_levels, format => '%s at %f line %i, log level: %l'
  min_level => 'warn', max_level => 'error',
));

like… it's giving "here's every way you could ever wire a logger up" and honestly? we love that for us 🫶

---

💖 DESCRIPTION

so this class is basically the main character of the logging pipeline: it receives log messages from an instance of Object::Remote::Logging::Router, formats them according to its configuration, and then outputs them straight to STDERR. 📤

and the little matchmaker sitting between the router and the logger? that's a selector method — it peeks at the log message metadata and returns 0 or more loggers that should receive that message. no cap, zero is a totally valid answer. 💅

---

🌸 USAGE

A logger object receives the log messages that get generated, converts them into formatted log entries, and then shows them to the end user. every logger has its own set of active log levels, and it will only output a log entry if the message lands on one of those active levels. picky? yes. correct? also yes. ✨

now, to actually get access to the stream of log messages, you make a connection to the log router. and you've got two flavors, bestie:

• A logger can connect directly to the router and receive an unfiltered stream of log messages.
• Or you can use a selector closure instead. 🦋

the selector gets executed for each log message along with the message metadata, and it returns a list of 0 or more loggers that should receive that message. when the selector runs:

1. the first argument is the name of the package that generated the log message
2. the second argument is a hash reference containing the message metadata

that's it, that's the contract. iykyk 😌

---

🦋 METADATA

the message metadata is a hash reference, and here are its keys — every single one, no skipping 👑

• message_level — name of the log level of the message.
• exporter — package name of the logging API that was used to generate the log message.
• caller_package — name of the package that generated the log message.
• method — name of the method the message was generated inside of.
• timestamp — Unix time of the message generation.
• pid — process id of the Perl interpreter the message was generated in.
• hostname — hostname of the system where the message was generated.
• filename — name of the file the message was generated in.
• line — line of the source file the message was generated at.
• object_remote — a reference to another hash holding the Object::Remote specific info. its keys are:
  • connection_id — if the log message was generated on a remote Perl interpreter, then the Object::Remote::Connection id of that interpreter will be available right here. 🌈

---

👑 ATTRIBUTES

okay bestie, here's where the configuration lives. read carefully, some of these have no default and that's not a drill 💀

💜 level_names

This is a required attribute. It must be an array ref with the list of log level names in it. the list must be ordered with the lowest level as element 0 and the highest level as the last element. there is no default value. fr fr, you have to pass it. 🙈

💜 min_level

The lowest log level that will be output by the logger. there is no default value.

💜 max_level

The highest log level that will be output by the logger. the default value is the highest level present in level_names. so like, it just figures it out for you. slay.

💜 format

The printf style format string used when rendering the log message. The following sequences are significant:

• %l — level name that the log message was generated at.
• %s — log message rendered into a string with a leading space before any additional lines in a multiple line message.
• %t — time the log message was generated rendered into a string. ⏰ the time value is taken from the Perl interpreter that generated the log message; it is not the time that the logger received the log message on the local interpreter if the log message was forwarded. important distinction, don't @ me.
• %r — Object::Remote connection information rendered into a string.
• %c — package name of the logging API that was used to generate the log message.
• %p — name of the package that generated the log message.
• %m — method name that generated the log message.
• %f — filename that the log message was generated in.
• %i — line number the log message was generated at.
• %h — hostname the log message was generated on.
• %P — process id of the Perl interpreter that generated the log message. (yes, capital P — lowercase p is the package, don't mix 'em up 💅)
• %% — a literal %.
• %n — a newline.

lowkey watch out for %P vs %p and %t vs everything else — the format string is doing a lot of heavy lifting here 🫶

---

and that's the whole page, bestie. go forth and log with main character energy. 🧚‍♀️💖

---

sign-off szn 🎀 — this page is from perl v5.40.2, dated 2026-07-16, and it's all Object:...::Logger(3) business. catch you in the next manpage, mwah 💋