From 6211cead7be6f0871cfcccccdfc00dbeb466bcf2 Mon Sep 17 00:00:00 2001
From: Siri Hansen
With this parameter, you can modify or disable the default - handler, add custom handlers and primary logger filters, and - set log levels per module.
+ handler, add custom handlers and primary logger filters, set + log levels per module, and modify + thefor each
Multiple entries of this type are allowed.
+Sets the proxy configuration, equivalent to calling
+++ logger:set_proxy_config(ProxyConfig) +
Only one entry of this type is allowed.
+See
section The Logger proxy is an Erlang process which is part of the
+ Kernel application's supervision tree. During startup, the proxy
+ process registers itself as the When a log event is issued on a process which has its group
+ leader on a remote node, Logger automatically forwards the log
+ event to the group leader's node. To achieve this, it first
+ sends the log event as an Erlang message from the original
+ client process to the proxy on the local node, and the proxy in
+ turn forwards the event to the proxy on the remote node. When receiving a log event, either from the emulator or from a
+ remote node, the proxy calls the Logger API to log the event. The proxy process is overload protected in the same way as
+ described in
+ section For log events from the emulator, synchronous message passing
+ mode is not applicable, since all messages are passed
+ asynchronously by the emulator. Drop mode is achieved by setting
+ the The proxy uses
+ #{sync_mode_qlen => 500,
+ drop_mode_qlen => 1000,
+ flush_qlen => 5000,
+ burst_limit_enable => false,
+ overload_kill_enable => false}
+