You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BEAM has a standard logger, and it has many features such as filters, error handling, multiple backends, dynamic configuration, and back pressure mechanisms to prevent a runaway logging process from causing performance problems.
It's a good point to support what is already standard in the BEAM in order to tap into already proven concepts. I will give it a try to fit this to the current architecture of Glimt. Some of the features are a bit overlapping (but of course the BEAM logger has a lot more features) but perhaps there is a good way of map the Glimt features onto the BEAM logger.
Hello!
The BEAM has a standard logger, and it has many features such as filters, error handling, multiple backends, dynamic configuration, and back pressure mechanisms to prevent a runaway logging process from causing performance problems.
https://www.erlang.org/doc/apps/kernel/logger_chapter.html
It would be fab to be able to use this library with the standard logger!
Thanks,
Louis
The text was updated successfully, but these errors were encountered: