Dancer2::Core::Role::Logger(3pm)

Dancer2::Core::Role::Logger3pm

Role for logger engines

Version

version 1.1.2

Overview

Any class that consumes this role will be able to implement to write log messages.

In order to implement this role, the consumer must implement the "log" method. This method will receives as argument the "level" and the "message".

Attributes

auto_encoding_charset

Charset to use when writing a message.

app_name

Name of the application. Can be used in the message.

log_format

This is a format string (or a preset name) to specify the log format.

The possible values are:

%a

app name

%h

host emitting the request

%t

date (local timezone, formatted like %d/%b/%Y %H:%M:%S)

%T

date (local timezone, formatted like %Y-%m-%d %H:%M:%S)

%u

date (UTC timezone, formatted like %d/%b/%Y %H:%M:%S)

%U

date (UTC timezone, formatted like %Y-%m-%d %H:%M:%S)

%P

PID

%L

log level

%D

timer

%m

message

%f

file name that emit the message

%l

line from the file

%i

request ID

%{$fmt}t

timer formatted with a valid time format

%{header}h

header value

log_level

Level to use by default.

Methods

core

Log messages as core.

debug

Log messages as debug.

info

Log messages as info.

warning

Log messages as warning.

error

Log messages as error.

format_message

Provides a common message formatting.

Configuration

The logger configuration variable tells Dancer2 which engine to use.

You can change it either in your config.yml file:

    # logging to console
    logger: "console"

The log format can also be configured, please see "log_format" in Dancer2::Core::Role::Logger for details.

Releases

6 releases since Debian 8 (Jessie); the text changed 5 times.

  1. 8
  2. 9
  3. 10
  4. 11
  5. 12
  6. 13

Author

Dancer Core Developers

From libdancer2-perl 1.1.2+dfsg-1 in Debian 13 (Trixie). Parsed by carta from the page's man source.