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
We should take in account fact that user can try to log a very large data (big lists and binaries, for example). We should trim such messages (this trimming should be enabled by default and one should have an ability to disable it). Also http://erlang.org/pipermail/erlang-questions/2011-July/060102.html
The text was updated successfully, but these errors were encountered:
I think we should do it only for our logs. I mean alog_tty, alog_disk_log, alog_syslog and scribe log.
When user implements his own logger, he should care about described problem. Alogger only sends data to loggers and we should not decide for a user what must be logged.
We should take in account fact that user can try to log a very large data (big lists and binaries, for example). We should trim such messages (this trimming should be enabled by default and one should have an ability to disable it). Also http://erlang.org/pipermail/erlang-questions/2011-July/060102.html
The text was updated successfully, but these errors were encountered: