| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
Log events issued via error_logger:info_msg or
error_logger:info_report are now forwarded to Logger with level
'notice' instead of 'info'.
Log events issued by gen_* behaviours are also changed from level
'info' to level 'notice'.
Progress reports are still 'info', and can therefore easily be
included/excluded by changing the primary log level. By default, they
are not logged.
|
|
Module and Id are now always included as fields in Config, so these
are no longer returned as separate elements.
|
|
And add field 'module' in handler config.
|
|
The warning map was added to allow backwards compatiblity with
error_logger event handlers that were not prepared to receive warning
reports. error_logger still uses this internally, if legacy error
logger event handlers are installed. But Logger does not use it for
new Logger handlers.
|
|
|
|
|
|
|
|
|
|
This function earlier only added/removed the old error_logger_tty_h
report handler. Since it is mostly used for turning off logging to tty
in general, it now also checks the default logger handlers. It works
as follows:
tty(true):
* If default handler is logger_std_h of type standard_io, make sure it
has no 'error_logger_tty_false filter'.
* Else, add a new instance of logger_std_h with type standard_io with
id 'error_logger_tty_true'.
tty(false):
* Remove error_logger_tty_h report handler if it exists.
* Remove error_logger_tty_false logger handler if it exists.
* If default handler is logger_std_h of type standard_io, add a filter
named 'error_logger_tty_false', which stops all events.
|
|
These are replaced by new config handling and must not be used any
more.
|
|
|
|
|
|
error_logger implements a simple handler which is used when no other
handler is active. This handler is used during system startup, when
there is no guarantee that all modules are loaded and must therefore
not use any other modules for the formatting.
Commit 41b856a2cb270ef807beaa84afe1bb890de5f237 introduced a call to
io_lib:printable_list/1, which is now removed.
|
|
If printable range is set to 'unicode', the simple error logger will now
recognize code points > 255 and print lists containing these as strings.
|
|
|
|
Calling error_logger:limit_term/1 before sending terms as events to
the error_logger can be used for limiting the size of the messages.
Doing so will not change the output, but potentially save memory.
The Kernel variable error_logger_format_depth is used when limiting
the size of terms.
|
|
|
|
Performance for processes that receive huge amounts of
messages can be increased by storing the incoming messages
outside the heap (that avoids copying the message in a
garbage collection).
Two OTP processes that are known to receive many messages
are 'rex' (used by 'rpc') and 'error_logger'.
|
|
|
|
* legoscia/prettier-default-error-logger/OTP-13325:
Prettify default error_logger output somewhat
|
|
The default error logger, the one in use before a more sophisticated
error logger can be installed, has rather terse output, in part because
it cannot rely on io:format. This patch attempts to improve the error
logger within that constraint:
- Print timestamps as YYYY-MM-DD HH:MM:SS
- For error reports with format strings, just print the format string
and the format arguments on separate lines
- For error reports with tuple lists, print each pair on a separate line
|
|
|
|
If the file given by the Kernel application variable 'error_logger'
cannot be opened a crash will occur.
|
|
|
|
|
|
|
