Erlang logging for the 21st OTP
summary
Compares lager to the new OTP 21 logger, showing OTP logger adds structured reports, per-event metadata, filters and multiple formatters but ships with unsafe defaults and can spike memory (tests show a console/file run hitting ~900 MB spikes on large messages). Benchmarks use log_bench and a cascading-fail test with message sizes 5 B, 56 B, 96 KB, 4 MB, 16 MB; a hybrid (logger formatter + OTP pipeline) outperforms defaults and lager plans a migration tool and parse-transform-based rewrite to map old APIs to the OTP logger.
AI-written summary · about
chapters (35)
- 0:00Introduction
- 0:14The importance of logs
- 1:51Why am I up here
- 2:53What is the problem with errorlog
- 4:58What was the whole
- 7:43Mistakes
- 10:11New Logger
- 11:33Thank you Eric
- 11:55OTP logger
- 14:10Chicken scroll
- 16:44Structured logging
- 17:47GenServer crashing
- 18:37Filters
- 20:26Backwards compatibility
- 21:53Whats next
- 22:40Logger 40 announcement
- 23:55Logger cheat sheet
- 25:15Why not keep it alive
- 25:59Community involvement
- 28:26Benchmarking
- 28:39Cascading failures
- 29:42Error logger
- 30:02Logger 40 alpha
- 31:10Logger 20 max
- 31:32Logger 20 console
- 32:03Formatter
- 32:16Benchmark
- 35:11Large messages
- 35:45Big messages
- 36:58Memory usage
- 37:14File memory usage
- 37:35Message sizes
- 39:20Wrapup
- 40:30Takeaway
- 40:54Questions
