lager is disabling logger default handler #492
Comments
|
I removed lager (and exometer) just because of this. Not saying that's a solution for everyone, but it did fix issues for me. |
benoitc
changed the title
|
I've also encountered this issue. Any solution on the road map? |
g-andrade
added a commit
to g-andrade/locus
that referenced
this issue
Aug 11, 2019
The way `error_logger` messages were forwarded to `logger` raised their level for undetermined reasons (e.g. an info message became a notice.) In order to fix this, invoke `logger` functions directly when they're available, *unless* `lager` is also present and has sabotaged the default `logger` handler, which would condemn our own `logger` messages into oblivion; in such cases, keep using `error_logger` as `lager` will display those messages properly in any case. Some information on the conflict between `logger` and `lager`: * erlang-lager/lager#492 * erlang-lager/lager#488
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
i commented 9f8d7a7#commitcomment-32283777 but since #481 any upstream application that rely on a library that forces the usage of lager doesn't log any more to the default handler when using logger. I would have expected to have them redirected like with the error_logger module.
Maybe using a logger handler that pass the input to lager would work?
The text was updated successfully, but these errors were encountered: