Global sasl filter of elixir means no logger handler can handle them

[lostko...@gmail.com]

Elixir currently uses a global setting for filtering out sasl reports. Now earlier this year I started work on porting nerves shoehorn to :logger from the deprecated :error_logger and it needs access to those sasl logs, but it doesn't really need the default logger handler handling sasl logs (or forcing users to enable that).

I'm wondering if elixir's logger filters should rather be opt in (filters on the default handler only, documented as options for custom handlers) vs primary filters, which apply to all handlers without "opt out".

[José Valim]

Please send a PR? I think it will be easier to visualize in this case. Before it was hard to do as a non-general handler but it may be attainable now.

On Mon, Jul 22, 2024 at 17:55 lostko...@gmail.com <lostko...@gmail.com> wrote:

Elixir currently uses a global setting for filtering out sasl reports. Now earlier this year I started work on porting nerves shoehorn to :logger from the deprecated :error_logger and it needs access to those sasl logs, but it doesn't really need the default logger handler handling sasl logs (or forcing users to enable that).

I'm wondering if elixir's logger filters should rather be opt in (filters on the default handler only, documented as options for custom handlers) vs primary filters, which apply to all handlers without "opt out".

--
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 elixir-lang-co...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/8c2aba5e-c2e5-44a8-8855-5cd6fca674een%40googlegroups.com.