Since Logger is new in Erlang/OTP 21.0, we do reserve the right to introduce changes to the Logger API and functionality in patches following this release. These changes might or might not be backwards compatible with the initial version.
logger
API module for Logger, the standard logging facility in Erlang/OTP.
This module implements the main API for logging in Erlang/OTP. To create a log event, use the API functions or the log macros, for example:
?LOG_ERROR("error happened because: ~p", [Reason]). % With macro
logger:error("error happened because: ~p", [Reason]). % Without macro To configure the Logger backend, use Kernel configuration parameters or configuration functions in the Logger API.
By default, the Kernel application installs one log handler at system start. This handler is named default. It receives and processes standard log events produced by the Erlang runtime system, standard behaviours and different Erlang/OTP applications. The log events are by default printed to the terminal.
If you want your systems logs to be printed to a file instead, you must configure the default handler to do so. The simplest way is to include the following in your sys.config:
[{kernel,
[{logger,
[{handler, default, logger_std_h,
#{config => #{type => {file, "path/to/file.log"}}}}]}]}]. For more information about:
User's Guide.Configuration section in the User's Guide.logger_std_h and logger_disk_log_h.logger_formatter.logger_filters.Since Logger is new in Erlang/OTP 21.0, we do reserve the right to introduce changes to the Logger API and functionality in patches following this release. These changes might or might not be backwards compatible with the initial version.
primary_config() =
#{level => level() | all | none,
filter_default => log | stop,
filters => [{filter_id(), filter()}]}Primary configuration data for Logger. The following default values apply:
level => infofilter_default => logfilters => []handler_config() =
#{id => handler_id(),
config => term(),
level => level() | all | none,
module => module(),
filter_default => log | stop,
filters => [{filter_id(), filter()}],
formatter => {module(), formatter_config()}}Handler configuration data for Logger. The following default values apply:
level => allfilter_default => logfilters => []formatter => {logger_formatter, DefaultFormatterConfig}In addition to these, the following fields are automatically inserted by Logger, values taken from the two first parameters to add_handler/3:
id => HandlerIdmodule => ModuleHandler specific configuration data is inserted by the handler callback itself, in a sub structure associated with the field named config.
See the logger_formatter(3) manual page for information about the default configuration for this formatter.
filter() =
{fun((log_event(), filter_arg()) -> filter_return()),
filter_arg()}A filter which can be installed as a handler filter, or as a primary filter in Logger.
filter_arg() = term()The second argument to the filter fun.
filter_id() = atom()A unique identifier for a filter.
filter_return() = stop | ignore | log_event()The return value from the filter fun.
formatter_config() = #{atom() => term()}Configuration data for the formatter. See logger_formatter(3) for an example of a formatter implementation.
handler_id() = atom()A unique identifier for a handler instance.
level() =
emergency |
alert |
critical |
error |
warning |
notice |
info |
debugThe severity level for the message to be logged.
log_event() =
#{level := level(),
msg :=
{io:format(), [term()]} |
{report, report()} |
{string, unicode:chardata()},
meta := metadata()}metadata() =
#{pid => pid(),
gl => pid(),
time => timestamp(),
mfa => {module(), atom(), integer() >= 0},
file => file:filename(),
line => integer() >= 0,
domain => [atom()],
report_cb => fun((report()) -> {io:format(), [term()]}),
atom() => term()}Metadata for the log event.
Logger adds the following metadata to each log event:
pid => self()gl => group_leader()time => erlang:system_time(microsecond)When a log macro is used, Logger also inserts location information:
mfa => {?MODULE, ?FUNCTION_NAME, ?FUNCTION_ARITY}file => ?FILEline => ?LINEYou can add custom metadata, either by specifying a map as the last parameter to any of the log macros or the API functions, or by setting process metadata with set_process_metadata/1 or update_process_metadata/1.
Logger merges all the metadata maps before forwarding the log event to the handlers. If the same keys occur, values from the log call overwrite process metadata, which in turn overwrite values set by Logger.
The following custom metadata keys have special meaning:
domainThe value associated with this key is used by filters for grouping log events originating from, for example, specific functional areas. See logger_filters:domain/2 for a description of how this field can be used.
report_cbIf the log message is specified as a report(), the report_cb key can be associated with a fun (report callback) that converts the report to a format string and arguments. See section Log Message in the User's Guide for more information about report callbacks.
msg_fun() =
fun((term()) ->
{io:format(), [term()]} |
report() |
unicode:chardata())report() = map() | [{atom(), term()}]timestamp() = integer()A timestamp produced with erlang:system_time(microsecond).
The following macros are defined:
?LOG_EMERGENCY(StringOrReport[,Metadata])?LOG_EMERGENCY(FunOrFormat,Args[,Metadata])?LOG_ALERT(StringOrReport[,Metadata])?LOG_ALERT(FunOrFormat,Args[,Metadata])?LOG_CRITICAL(StringOrReport[,Metadata])?LOG_CRITICAL(FunOrFormat,Args[,Metadata])?LOG_ERROR(StringOrReport[,Metadata])?LOG_ERROR(FunOrFormat,Args[,Metadata])?LOG_WARNING(StringOrReport[,Metadata])?LOG_WARNING(FunOrFormat,Args[,Metadata])?LOG_NOTICE(StringOrReport[,Metadata])?LOG_NOTICE(FunOrFormat,Args[,Metadata])?LOG_INFO(StringOrReport[,Metadata])?LOG_INFO(FunOrFormat,Args[,Metadata])?LOG_DEBUG(StringOrReport[,Metadata])?LOG_DEBUG(FunOrFormat,Args[,Metadata])All macros expand to a call to Logger, where Level is taken from the macro name, and location data is added to the metadata. See the description of the metadata() type for more information about the location data.
The call is wrapped in a case statement and will be evaluated only if Level is equal to or below the configured log level.
Equivalent to log(emergency,...).
Equivalent to log(alert,...).
Equivalent to log(critical,...).
Equivalent to log(error,...).
Equivalent to log(warning,...).
Equivalent to log(notice,...).
Equivalent to log(info,...).
Equivalent to log(debug,...).
Log the given message.
Add a handler with the given configuration.
HandlerId is a unique identifier which must be used in all subsequent calls referring to this handler.
Add a filter to the specified handler.
The filter fun is called with the log event as the first parameter, and the specified filter_args() as the second parameter.
The return value of the fun specifies if a log event is to be discarded or forwarded to the handler callback:
log_event()The filter passed. The next handler filter, if any, is applied. If no more filters exist for this handler, the log event is forwarded to the handler callback.
stopThe filter did not pass, and the log event is immediately discarded.
ignoreThe filter has no knowledge of the log event. The next handler filter, if any, is applied. If no more filters exist for this handler, the value of the filter_default configuration parameter for the handler specifies if the log event shall be discarded or forwarded to the handler callback.
See section Filters in the User's Guide for more information about filters.
Some built-in filters exist. These are defined in logger_filters.
Reads the application configuration parameter logger and calls add_handlers/1 with its contents.
This function should be used by custom Logger handlers to make configuration consistent no matter which handler the system uses. Normal usage is to add a call to logger:add_handlers/1 just after the processes that the handler needs are started, and pass the application's logger configuration as the argument. For example:
-behaviour(application).
start(_, []) ->
case supervisor:start_link({local, my_sup}, my_sup, []) of
{ok, Pid} ->
ok = logger:add_handlers(my_app),
{ok, Pid, []};
Error -> Error
end. This reads the logger configuration parameter from the my_all application and starts the configured handlers. The contents of the configuration use the same rules as the logger handler configuration.
If the handler is meant to replace the default handler, the Kernel's default handler have to be disabled before the new handler is added. A sys.config file that disables the Kernel handler and adds a custom handler could look like this:
[{kernel,
[{logger,
%% Disable the default Kernel handler
[{handler, default, undefined}]}]},
{my_app,
[{logger,
%% Enable this handler as the default
[{handler, default, my_handler, #{}}]}]}].
Add a primary filter to Logger.
The filter fun is called with the log event as the first parameter, and the specified filter_args() as the second parameter.
The return value of the fun specifies if a log event is to be discarded or forwarded to the handlers:
log_event()The filter passed. The next primary filter, if any, is applied. If no more primary filters exist, the log event is forwarded to the handler part of Logger, where handler filters are applied.
stopThe filter did not pass, and the log event is immediately discarded.
ignoreThe filter has no knowledge of the log event. The next primary filter, if any, is applied. If no more primary filters exist, the value of the primary filter_default configuration parameter specifies if the log event shall be discarded or forwarded to the handler part.
See section Filters in the User's Guide for more information about filters.
Some built-in filters exist. These are defined in logger_filters.
primary_config(),handler_config()],level() | all | none}]}Look up all current Logger configuration, including primary and handler configuration, and module level settings.
Look up the current configuration for all handlers.
Look up the current configuration for the given handler.
Look up the identities for all installed handlers.
Look up the current primary configuration for Logger.
Look up all current module levels. Returns a list containing one {Module,Level} element for each module for which the module level was previously set with set_module_level/2.
Look up the current level for the given modules. Returns a list containing one {Module,Level} element for each of the given modules for which the module level was previously set with set_module_level/2.
Retrieve data set with set_process_metadata/1 or update_process_metadata/1.
Remove the handler identified by HandlerId.
Remove the filter identified by FilterId from the handler identified by HandlerId.
Remove the primary filter identified by FilterId from Logger.
Set configuration data for the specified handler. This overwrites the current handler configuration.
To modify the existing configuration, use update_handler_config/2, or, if a more complex merge is needed, read the current configuration with get_handler_config/1, then do the merge before writing the new configuration back with this function.
If a key is removed compared to the current configuration, and the key is known by Logger, the default value is used. If it is a custom key, then it is up to the handler implementation if the value is removed or a default value is inserted.
Add or update configuration data for the specified handler. If the given Key already exists, its associated value will be changed to Value. If it does not exist, it will be added.
Set primary configuration data for Logger. This overwrites the current configuration.
To modify the existing configuration, use update_primary_config/1, or, if a more complex merge is needed, read the current configuration with get_primary_config/0, then do the merge before writing the new configuration back with this function.
If a key is removed compared to the current configuration, the default value is used.
Add or update primary configuration data for Logger. If the given Key already exists, its associated value will be changed to Value. If it does not exist, it will be added.
Set the log level for the specified modules.
The log level for a module overrides the primary log level of Logger for log events originating from the module in question. Notice, however, that it does not override the level configuration for any handler.
For example: Assume that the primary log level for Logger is info, and there is one handler, h1, with level info and one handler, h2, with level debug.
With this configuration, no debug messages will be logged, since they are all stopped by the primary log level.
If the level for mymodule is now set to debug, then debug events from this module will be logged by the handler h2, but not by handler h1.
Debug events from other modules are still not logged.
To change the primary log level for Logger, use set_primary_config(level, Level).
To change the log level for a handler, use set_handler_config(HandlerId, level, Level).
The originating module for a log event is only detected if the key mfa exists in the metadata, and is associated with {Module, Function, Arity}. When log macros are used, this association is automatically added to all log events. If an API function is called directly, without using a macro, the logging client must explicitly add this information if module levels shall have any effect.
Set metadata which Logger shall automatically insert in all log events produced on the current process.
Location data produced by the log macros, and/or metadata given as argument to the log call (API function or macro), are merged with the process metadata. If the same keys occur, values from the metadata argument to the log call overwrite values from the process metadata, which in turn overwrite values from the location data.
Subsequent calls to this function overwrites previous data set. To update existing data instead of overwriting it, see update_process_metadata/1.
Remove module specific log settings. After this, the primary log level is used for all modules.
Remove module specific log settings. After this, the primary log level is used for the specified modules.
Delete data set with set_process_metadata/1 or update_process_metadata/1.
Update the formatter configuration for the specified handler.
The new configuration is merged with the existing formatter configuration.
To overwrite the existing configuration without any merge, use
set_handler_config(HandlerId, formatter, {FormatterModule, FormatterConfig}).
Update the formatter configuration for the specified handler.
This is equivalent to
update_formatter_config(HandlerId, #{Key=>Value})
Update configuration data for the specified handler. This function behaves as if it was implemented as follows:
{ok, {_, Old}} = logger:get_handler_config(HandlerId),
logger:set_handler_config(HandlerId, maps:merge(Old, Config)). To overwrite the existing configuration without any merge, use set_handler_config/2.
Update primary configuration data for Logger. This function behaves as if it was implemented as follows:
Old = logger:get_primary_config(), logger:set_primary_config(maps:merge(Old, Config)).
To overwrite the existing configuration without any merge, use set_primary_config/1.
Set or update metadata to use when logging from current process
If process metadata exists for the current process, this function behaves as if it was implemented as follows:
logger:set_process_metadata(maps:merge(logger:get_process_metadata(), Meta)).
If no process metadata exists, the function behaves as set_process_metadata/1.
Compare the severity of two log levels. Returns gt if Level1 is more severe than Level2, lt if Level1 is less severe, and eq if the levels are equal.
Convert a log message on report form to {Format, Args}. This is the default report callback used by logger_formatter when no custom report callback is found. See section Log Message in the Kernel User's Guide for information about report callbacks and valid forms of log messages.
The function produces lines of Key: Value from key-value lists. Strings are printed with ~ts and other terms with ~tp.
If Report is a map, it is converted to a key-value list before formatting as such.
The following functions are to be exported from a handler callback module.
This callback function is optional.
The function is called on a temporary process when an new handler is about to be added. The purpose is to verify the configuration and initiate all resources needed by the handler.
The handler identity is associated with the id key in Config1.
If everything succeeds, the callback function can add possible default values or internal state values to the configuration, and return the adjusted map in {ok,Config2}.
If the configuration is faulty, or if the initiation fails, the callback function must return {error,Reason}.
This callback function is optional.
The function is called on a temporary process when the configuration for a handler is about to change. The purpose is to verify and act on the new configuration.
Config1 is the existing configuration and Config2 is the new configuration.
The handler identity is associated with the id key in Config1.
If everything succeeds, the callback function must return a possibly adjusted configuration in {ok,Config3}.
If the configuration is faulty, the callback function must return {error,Reason}.
This callback function is mandatory.
The function is called when all primary filters and all handler filters for the handler in question have passed for the given log event. It is called on the client process, that is, the process that issued the log event.
The handler identity is associated with the id key in Config.
The handler must log the event.
The return value from this function is ignored by Logger.
This callback function is optional.
The function is called on a temporary process when a handler is about to be removed. The purpose is to release all resources used by the handler.
The handler identity is associated with the id key in Config.
The return value is ignored by Logger.
The following functions are to be exported from a formatter callback module.
This callback function is optional.
The function is called by a Logger when formatter configuration is set or modified. The formatter must validate the given configuration and return ok if it is correct, and {error,Reason} if it is faulty.
The following Logger API functions can trigger this callback:
logger:add_handler/3logger:set_handler_config/2,3logger:updata_handler_config/2logger:update_formatter_config/2See logger_formatter(3) for an example implementation. logger_formatter is the default formatter used by Logger.
This callback function is mandatory.
The function can be called by a log handler to convert a log event term to a printable string. The returned value can, for example, be printed as a log entry to the console or a file using io:put_chars/1,2.
See logger_formatter(3) for an example implementation. logger_formatter is the default formatter used by Logger.
config(4), erlang(3), io(3), logger_disk_log_h(3), logger_filters(3), logger_formatter(3), logger_std_h(3), unicode(3)
© 2010–2017 Ericsson AB
Licensed under the Apache License, Version 2.0.