Wow, thanks Ryan, It's really something that I would expect from a decent logging framework. For sure, that'll (lager) be something that I'll be using in my applications in the future.
Alin. On Mon, Feb 6, 2012 at 10:00 PM, Ryan Zezeski <[email protected]> wrote: > Alin, > > Lager is flexible like that. If you notice the error counts incrementing > then you can do something like the following at the Riak console. > > {ok, Trace} = lager:trace_file("<path>/failing-postcommits", [{module, > riak_kv_put_fsm}, {function, decode_postcommit}], debug). > > That should send any debug msgs originating from that module + function to > the <path>/failing-postcommits file. To stop the trace run the following: > > lager:stop_trace(Trace). > > -Ryan > > > On Sat, Feb 4, 2012 at 1:04 AM, Alin Popa <[email protected]> wrote: > >> Ok, that makes sense; but, what if another approach is picked up, like >> being able to tune this specific logging separately ? Or have the lager >> being able to log messages on different files per module/function - that >> way the logging flood would be isolated only to this... >> Sorry for being so insistent regarding this matter, but it seems that >> post commits are a pretty neat feature which we're not able to use because >> of this exception/error handling inconvenient. >> >> Thanks, >> Alin >> >> >> >> On 4 Feb 2012, at 00:12, Andrew Thompson <[email protected]> wrote: >> >> > On Fri, Feb 03, 2012 at 11:44:49PM +0200, Alin Popa wrote: >> >> Ryan, >> >> >> >> I would say that having those informations into the log files, >> especially >> >> the reason why it failed, is very useful, so, would you say it would be >> >> helpful if I'm going to open a pull request which will increase the log >> >> level usage from debug to error for pre/post commit hooks execution >> errors >> >> (as it seems to be pretty straight forward) ? >> >> >> > The reason we put it at the debug level is to avoid logging flood when >> > you break a postcommit hook in production and all your postcommits start >> > to fail. If you're doing thousands of writes per second, that would >> > obviously be bad. >> > >> > Andrew >> > >> > _______________________________________________ >> > riak-users mailing list >> > [email protected] >> > http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> >> _______________________________________________ >> riak-users mailing list >> [email protected] >> http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com >> > >
_______________________________________________ riak-users mailing list [email protected] http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
