From 5e23103186cb71c64f7f2fa28cbfd8c62d7ee21b Mon Sep 17 00:00:00 2001
From: Siri Hansen 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. This callback function is optional. The function is called when an new handler is about to be
- added, and the purpose is to verify the configuration and
- initiate all resources needed by the handler. 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 If everything succeeds, the callback function can add
@@ -972,9 +982,9 @@ logger:set_process_metadata(maps:merge(logger:get_process_metadata(), Meta)).
This callback function is optional. The function is called when the configuration for a handler
- is about to change, and the purpose is to verify and act on
- the new configuration. 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. The handler identity is associated with the 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. The handler identity is associated with the The handler must log the event. This callback function is optional. The function is called when a handler is about to be
- removed, and the purpose is to release all resources used by
- the handler. 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 The return value is ignored by Logger.
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.
+A log event consists of a log level, the
@@ -84,11 +91,11 @@
section
If a log event passes through all primary filters and all
- handler filters for a specific handler, Logger forwards the event
- to the handler callback. The handler formats and prints the
- event to its destination. See
- section
Everything up to and including the call to the handler
callbacks is executed on the client process, that is, the
process where the log event was issued. It is up to the handler
@@ -113,10 +120,11 @@
The log level indicates the severity of a event. In - accordance with the Syslog protocol, RFC-5424, eight log - levels can be specified. The following table lists all - possible log levels by name (atom), integer value, and - description:
+ accordance with the Syslog protocol, +