[erlang-questions] Simple Logging
Dmitry Kolesnikov
dmkolesnikov@REDACTED
Mon Feb 3 23:06:28 CET 2014
Hello,
You are looking for +W flag, e.g. erl +W i should make a trick for you.
+W w | i
Sets the mapping of warning messages for error_logger. Messages sent to the error logger using one of the warning routines can be mapped either to errors (default), warnings (+W w), or info reports (+W i). The current mapping can be retrieved using error_logger:warning_map/0. See error_logger(3) for further information.
However, I would still advice to use lagger. It is compatible with error_logger framework and nicely cooperates with legacy code. Long time ago, I’ve passed through your dilemma, as the result. I’ve end-up with lagger.
BTW, I am also confused with goldrush dependencies in lager. I guess it is used to manage flow control to std io.
- Dmitry
On 03 Feb 2014, at 23:29, Niklas Semmler <semmler@REDACTED> wrote:
> The code I am working on is supposed to be integrated with a bigger system later on. As far as I know the other system uses native logging.
>
> That's why I want to avoid Lager. I would rather work out my own get_event..
>
> -- Niklas
>
> On Feb 3, 2014, at 9:51 PM, Jesper Louis Andersen wrote:
>
>> On Mon, Feb 3, 2014 at 7:20 PM, Niklas Semmler <semmler@REDACTED> wrote:
>>
>>> PS: Lager is unfortunately not an option as I have to avoid any
>>> unnecessary dependencies.
>>
>>
>> You really want lager for this. What is the rationale for avoiding an
>> unnecessary dependency?
>>
>>
>> --
>> J.
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20140204/df0af624/attachment.htm>
More information about the erlang-questions
mailing list