Having recently made the journey from Java to Elixir I was also struck by the inflexibility of the built-in logging framework. The inability to configure log levels per module/application lead me to create FlexLogger ( https://hex.pm/packages/flex_logger) which, however, is a crude substitute for a built-in solution with compile-time purging as it performs run-time checks.
Besides, I would also like to argue for an extra log level for trace messages. While usually the existing log levels are sufficient there are cases where you would like to have the ability to, for example, log every single message coming to a genserver. For most cases this would be a total overkill of messages and in particular the high amount might lead to logs being unreadable. But for understanding what goes on in this particular genserver these kinds of logs could be invaluable. For now, I am usually commenting out debug messages of the trace type (or most often I am actually deleting them once I think everything is fine) and add them back when needed. So I for one would be very happy with an additional log level (especially in combination with module/application specific setting of log levels). Arno -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/b108e778-e883-4ab3-99d6-6f1bb215123c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
