<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hello,<br>
<br>
from what I read about the error_logger "Error, warning and info
events are sent to the error logger from the Erlang runtime system
and the different Erlang/OTP applications." So, I guess, errors in
non-supervised code are also sent to the error_logger. But not to
lager's crash file. Actually this badmatch error is not reported
anywhere. How can I make lager report it?<br>
<br>
Regards,<br>
Martin<br>
<br>
<div class="moz-cite-prefix">On 1/22/2016 7:55 PM, Nathaniel
Waisbrot wrote:<br>
</div>
<blockquote
cite="mid:E71C18FB-EBB6-4B93-A6EF-95B848A379B7@waisbrot.net"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=windows-1252">
<div class="">
<blockquote type="cite" class="">
<div class="">dummy = <a class="moz-txt-link-freetext" href="application:get_env(myapp">application:get_env(myapp</a>, test).</div>
<div class=""><br class="">
This results in badmatch. But there is no entry in
crash.log. I had<br class="">
configured another log file warning.log that gets populated
with a<br class="">
one-liner but I would like to see the detailed report in
crash.log.<br class="">
</div>
</blockquote>
</div>
<div class=""><br class="">
</div>
<div class=""><br class="">
</div>
<div class="">The crash.log comes from things that use the
error_logger (<a moz-do-not-send="true"
href="http://erlang.org/doc/man/error_logger.html" class="">http://erlang.org/doc/man/error_logger.html</a>).
Typically, this is OTP applications crashing.</div>
<div class=""><br class="">
</div>
<div class="">Try putting that badmatch inside of a gen_server's
handle_cast/3 method and you should see lager's handling (and if
you disable crash logging in lager you can see what the default
error_logger does with it).</div>
<div class=""><br class="">
</div>
</blockquote>
<br>
</body>
</html>