Logger

A logger for Elixir applications.

It includes many features:

Provides debug, info, warn, and error levels.
Supports multiple backends which are automatically supervised when plugged into Logger.
Formats and truncates messages on the client to avoid clogging Logger backends.
Alternates between sync and async modes to remain performant when required but also apply backpressure when under stress.
Wraps OTP’s error_logger to prevent it from overflowing.

Logging is useful for tracking when an event of interest happens in your system. For example, it may be helpful to log whenever a user is deleted.

def delete_user(user) do
  Logger.info fn ->
    "Deleting user from the system: #{inspect(user)}"
  end
  # ...
end

The Logger.info/2 macro emits the provided message at the :info level. There are additional macros for other levels. Notice the argument passed to Logger.info/2 in the above example is a zero argument function.

Although the Logger macros accept messages as strings as well as functions, it’s recommended to use functions whenever the message is expensive to compute. In the example above, the message is evaluated (and thus so is the interpolation inside it) regardless of the level, even if the message will not be actually logged at runtime; the only way of avoiding evaluation of such message is purging the log call at compile-time through the :compile_time_purge_level option (see below), or using a function that is evaluated to generate the message only if the message needs to be logged according to the runtime level.

Levels

The supported levels are:

:debug - for debug-related messages
:info - for information of any kind
:warn - for warnings
:error - for errors

Configuration

Logger supports a wide range of configurations.

This configuration is split in three categories:

Application configuration - must be set before the :logger application is started
Runtime configuration - can be set before the :logger application is started, but may be changed during runtime
Error logger configuration - configuration for the wrapper around OTP’s error_logger

Application configuration

The following configuration must be set via config files (such as config/config.exs) before the :logger application is started.

:backends - the backends to be used. Defaults to [:console]. See the “Backends” section for more information.
:compile_time_purge_level - purges at compilation time all calls that have log level lower than the value of this option. This means that Logger calls with level lower than this option will be completely removed at compile time, accruing no overhead at runtime. Defaults to :debug and only applies to the Logger.debug/2, Logger.info/2, Logger.warn/2, and Logger.error/2 macros (for example, it doesn’t apply to Logger.log/3). Note that arguments passed to Logger calls that are removed from the AST at compilation time are never evaluated, thus any function call that occurs in these arguments is never executed. As a consequence, avoid code that looks like Logger.debug("Cleanup: #{perform_cleanup()}") as in the example perform_cleanup/0 won’t be executed if the :compile_time_purge_level is :info or higher.
:compile_time_application - sets the :application metadata value to the configured value at compilation time. This configuration is usually only useful for build tools to automatically add the application to the metadata for Logger.debug/2, Logger.info/2, etc. style of calls.

For example, to configure the :backends and compile_time_purge_level options in a config/config.exs file:

config :logger,
  backends: [:console],
  compile_time_purge_level: :info

Runtime Configuration

All configuration below can be set via config files (such as config/config.exs) but also changed dynamically during runtime via Logger.configure/1.

:level - the logging level. Attempting to log any message with severity less than the configured level will simply cause the message to be ignored. Keep in mind that each backend may have its specific level, too. Note that, unlike what happens with the :compile_time_purge_level option, the argument passed to Logger calls is evaluated even if the level of the call is lower than :level. For this reason, messages that are expensive to compute should be wrapped in 0-arity anonymous functions that are evaluated only when the :label option demands it.
:utc_log - when true, uses UTC in logs. By default it uses local time (i.e., it defaults to false).
:truncate - the maximum message size to be logged (in bytes). Defaults to 8192 bytes. Note this configuration is approximate. Truncated messages will have " (truncated)" at the end. The atom :infinity can be passed to disable this behavior.
:sync_threshold - if the Logger manager has more than :sync_threshold messages in its queue, Logger will change to sync mode, to apply backpressure to the clients. Logger will return to async mode once the number of messages in the queue is reduced to sync_threshold * 0.75 messages. Defaults to 20 messages.
:translator_inspect_opts - when translating OTP reports and errors, the last message and state must be inspected in the error reports. This configuration allow developers to change how much and how the data should be inspected.

For example, to configure the :level and :truncate options in a config/config.exs file:

config :logger,
  level: :warn,
  truncate: 4096

Error logger configuration

The following configuration applies to Logger’s wrapper around Erlang’s error_logger. All the configurations below must be set before the :logger application starts.

:handle_otp_reports - redirects OTP reports to Logger so they are formatted in Elixir terms. This uninstalls Erlang’s logger that prints terms to terminal. Defaults to true.
:handle_sasl_reports - redirects supervisor, crash and progress reports to Logger so they are formatted in Elixir terms. Your application must guarantee :sasl is started before :logger. This means you may see some initial reports written in Erlang syntax until the Logger application kicks in and uninstalls SASL’s logger in favor of its own. Defaults to false.
:discard_threshold_for_error_logger - a value that, when reached, triggers the error logger to discard messages. This value must be a positive number that represents the maximum number of messages accepted per second. Once above this threshold, the error_logger enters discard mode for the remainder of that second. Defaults to 500 messages.

For example, to configure Logger to redirect all error_logger messages using a config/config.exs file:

config :logger,
  handle_otp_reports: true,
  handle_sasl_reports: true

Furthermore, Logger allows messages sent by Erlang’s error_logger to be translated into an Elixir format via translators. Translators can be dynamically added at any time with the add_translator/1 and remove_translator/1 APIs. Check Logger.Translator for more information.

Backends

Logger supports different backends where log messages are written to.

The available backends by default are:

:console - logs messages to the console (enabled by default)

Developers may also implement their own backends, an option that is explored in more detail below.

The initial backends are loaded via the :backends configuration, which must be set before the :logger application is started.

Console backend

The console backend logs messages by printing them to the console. It supports the following options:

:level - the level to be logged by this backend. Note that messages are filtered by the general :level configuration for the :logger application first.
:format - the format message used to print logs. Defaults to: "\n$time $metadata[$level] $levelpad$message\n". It may also be a {module, function} tuple that is invoked with the log level, the message, the current timestamp and the metadata.
:metadata - the metadata to be printed by $metadata. Defaults to an empty list (no metadata). Setting :metadata to :all prints all metadata.
:colors - a keyword list of coloring options.
:device - the device to log error messages to. Defaults to :user but can be changed to something else such as :standard_error.
:max_buffer - maximum events to buffer while waiting for a confirmation from the IO device (default: 32). Once the buffer is full, the backend will block until a confirmation is received.

In addition to the keys provided by the user via Logger.metadata/1, the following extra keys are available to the :metadata list:

:application - the current application
:module - the current module
:function - the current function
:file - the current file
:line - the current line
:pid - the current process ID

The supported keys in the :colors keyword list are:

:enabled - boolean value that allows for switching the coloring on and off. Defaults to: IO.ANSI.enabled?/0
:debug - color for debug messages. Defaults to: :cyan
:info - color for info messages. Defaults to: :normal
:warn - color for warn messages. Defaults to: :yellow
:error - color for error messages. Defaults to: :red

See the IO.ANSI module for a list of colors and attributes.

Here is an example of how to configure the :console backend in a config/config.exs file:

config :logger, :console,
  format: "\n$time $metadata[$level] $levelpad$message\n",
  metadata: [:user_id]

Custom Formatting

The console backend allows you to customize the format of your log messages with the :format option.

You may set :format to either a string or a {module, function} tuple if you wish to provide your own format function. The {module, function} will be invoked with the log level, the message, the current timestamp and the metadata.

Here is an example of how to configure the :console backend in a config/config.exs file:

config :logger, :console,
  format: {MyConsoleLogger, :format}

And here is an example of how you can define MyConsoleLogger.format/4 from the above configuration.

defmodule MyConsoleLogger do
  def format(level, message, timestamp, metadata) do
    # Custom formatting logic...
  end
end

You can read more about formatting in Logger.Formatter.

Custom backends

Any developer can create their own Logger backend. Since Logger is an event manager powered by :gen_event, writing a new backend is a matter of creating an event handler, as described in the :gen_event documentation.

From now on, we will be using the term “event handler” to refer to your custom backend, as we head into implementation details.

Once the :logger application starts, it installs all event handlers listed under the :backends configuration into the Logger event manager. The event manager and all added event handlers are automatically supervised by Logger.

Once initialized, the handler should be designed to handle events in the following format:

{level, group_leader, {Logger, message, timestamp, metadata}} | :flush

where:

level is one of :debug, :info, :warn, or :error, as previously described
group_leader is the group leader of the process which logged the message
{Logger, message, timestamp, metadata} is a tuple containing information about the logged message:
- the first element is always the atom Logger
- message is the actual message (as chardata)
- timestamp is the timestamp for when the message was logged, as a {{year, month, day}, {hour, minute, second, millisecond}} tuple
- metadata is a keyword list of metadata used when logging the message

It is recommended that handlers ignore messages where the group leader is in a different node than the one where the handler is installed. For example:

def handle_event({_level, gl, {Logger, _, _, _}}, state)
    when node(gl) != node() do
  {:ok, state}
end

In the case of the event :flush handlers should flush any pending data. This event is triggered by flush/0.

Furthermore, backends can be configured via the configure_backend/2 function which requires event handlers to handle calls of the following format:

{:configure, options}

where options is a keyword list. The result of the call is the result returned by configure_backend/2. The recommended return value for successful configuration is :ok.

It is recommended that backends support at least the following configuration options:

:level - the logging level for that backend
:format - the logging format for that backend
:metadata - the metadata to include in that backend

Check the implementation for Logger.Backends.Console, for examples on how to handle the recommendations in this section and how to process the existing options.

Summary

Functions

add_backend(backend, opts \\ []): Adds a new backend
add_translator(translator): Adds a new translator
bare_log(level, chardata_or_fun, metadata \\ []): Logs a message dynamically
compare_levels(level, level): Compares log levels
configure(options): Configures the logger
configure_backend(backend, options): Configures the given backend
debug(chardata_or_fun, metadata \\ []): Logs a debug message
disable(pid): Disables logging for the current process
enable(pid): Enables logging for the current process
error(chardata_or_fun, metadata \\ []): Logs an error message
flush(): Flushes the logger
info(chardata_or_fun, metadata \\ []): Logs an info message
level(): Retrieves the Logger level
log(level, chardata_or_fun, metadata \\ []): Logs a message with the given level
metadata(): Reads the current process metadata
metadata(keyword): Alters the current process metadata according the given keyword list
remove_backend(backend, opts \\ []): Removes a backend
remove_translator(translator): Removes a translator
reset_metadata(keywords \\ []): Resets the current process metadata to the given keyword list
warn(chardata_or_fun, metadata \\ []): Logs a warning message

Types

backend()

backend() :: :gen_event.handler()

level()

level() :: :error | :info | :warn | :debug

message()

message() :: IO.chardata() | String.Chars.t()

metadata()

metadata() :: keyword(String.Chars.t())

Functions

add_backend(backend, opts \\ [])

add_backend(atom(), keyword()) :: Supervisor.on_start_child()

Adds a new backend.

Options

:flush - when true, guarantees all messages currently sent to both Logger and Erlang’s error_logger are processed before the backend is added

add_translator(translator)

add_translator({module(), function :: atom()}) :: :ok

Adds a new translator.

bare_log(level, chardata_or_fun, metadata \\ [])

bare_log(level(), message() | (() -> message() | {message(), keyword()}), keyword()) ::
  :ok |
  {:error, :noproc} |
  {:error, term()}

Logs a message dynamically.

Use this function only when there is a need to explicitly avoid embedding metadata.

compare_levels(level, level)

compare_levels(level(), level()) :: :lt | :eq | :gt

Compares log levels.

Receives two log levels and compares the left level against the right level and returns

:lt if left is less than right
:eq if left and right are equal
:gt if left is greater than right

Examples

iex> Logger.compare_levels(:debug, :warn)
:lt
iex> Logger.compare_levels(:error, :info)
:gt

configure(options)

configure(keyword()) :: :ok

Configures the logger.

See the “Runtime Configuration” section in the Logger module documentation for the available options.

configure_backend(backend, options)

configure_backend(backend(), keyword()) :: term()

Configures the given backend.

The backend needs to be started and running in order to be configured at runtime.

debug(chardata_or_fun, metadata \\ []) (macro)

Logs a debug message.

Returns :ok or an {:error, reason} tuple.

Examples

Logger.debug "hello?"
Logger.debug fn -> "expensive to calculate debug" end
Logger.debug fn -> {"expensive to calculate debug", [additional: :metadata]} end

disable(pid)

disable(pid()) :: :ok

Disables logging for the current process.

Currently the only accepted PID is self().

enable(pid)

enable(pid()) :: :ok

Enables logging for the current process.

Currently the only accepted PID is self().

error(chardata_or_fun, metadata \\ []) (macro)

Logs an error message.

Returns :ok or an {:error, reason} tuple.

Examples

Logger.error "oops"
Logger.error fn -> "expensive to calculate error" end
Logger.error fn -> {"expensive to calculate error", [additional: :metadata]} end

flush()

flush() :: :ok

Flushes the logger.

This guarantees all messages sent to Logger prior to this call will be processed. This is useful for testing and it should not be called in production code.

info(chardata_or_fun, metadata \\ []) (macro)

Logs an info message.

Returns :ok or an {:error, reason} tuple.

Examples

Logger.info "mission accomplished"
Logger.info fn -> "expensive to calculate info" end
Logger.info fn -> {"expensive to calculate info", [additional: :metadata]} end

level()

level() :: level()

Retrieves the Logger level.

The Logger level can be changed via configure/1.

log(level, chardata_or_fun, metadata \\ []) (macro)

Logs a message with the given level.

Returns :ok or an {:error, reason} tuple.

The macros debug/2, warn/2, info/2, and error/2 are preferred over this macro as they can automatically eliminate the call to Logger alotgether at compile time if desired (see the documentation for the Logger module).

metadata()

metadata() :: metadata()

Reads the current process metadata.

metadata(keyword)

metadata(metadata()) :: :ok

Alters the current process metadata according the given keyword list.

This function will merge the given keyword list into the existing metadata, with the exception of setting a key to nil, which will remove that key from the metadata.

remove_backend(backend, opts \\ [])

remove_backend(atom(), keyword()) :: :ok | {:error, term()}

Removes a backend.

Options

:flush - when true, guarantees all messages currently sent to both Logger and Erlang’s error_logger are processed before the backend is removed

remove_translator(translator)

remove_translator({module(), function :: atom()}) :: :ok

Removes a translator.

reset_metadata(keywords \\ [])

reset_metadata(metadata()) :: :ok

Resets the current process metadata to the given keyword list.

warn(chardata_or_fun, metadata \\ []) (macro)

Logs a warning message.

Returns :ok or an {:error, reason} tuple.

Examples

Logger.warn "knob turned too far to the right"
Logger.warn fn -> "expensive to calculate warning" end
Logger.warn fn -> {"expensive to calculate warning", [additional: :metadata]} end

Name	Elixir
Version
Badge
Last Updated	2019-08-22T13:17:40Z