Hey Bryan, Something similar in the RabbitMQ code base made me go "huh" the other day. Calls to rabbit_log_ldap module functions when no such module exists. Turns out there's a parse transform defined that turns these calls into lager function calls to an extra sink:
https://github.com/rabbitmq/rabbitmq-common/blob/master/mk/rabbitmq-build.mk#L46 I couldn't find any instance of object_lager_event:info (debug, warning, etc) function calls in the Riak code I have lying around, though, so /shrug Good luck - Luke On Mon, Oct 21, 2019 at 9:18 AM Bryan Hunt <bryan.h...@erlang-solutions.com> wrote: > > Given the following configuration, can anyone explain to me what the > object_lager_event section does? > > I see this code all over the place (including snippets I provided in the > distant past). > > However, a search on github (basho org/erlang-lager/lager) don’t throw up any > code/module matches. > > (GitHub indexing doesn’t work well as GitHub only index master and basho > stuff is a mess branch wise). > > Anyone got any idea ? > > [ > {lager, > [ > {extra_sinks, > [ > {object_lager_event, > [{handlers, > [{lager_file_backend, > [{file, "/var/log/riak/object.log"}, > {level, info}, > {formatter_config, [date, " ", time," [",severity,"] > ",message, "\n"]} > ] > }] > }, > {async_threshold, 500}, > {async_threshold_window, 50}] > } > ] > } > ] > }] _______________________________________________ riak-users mailing list riak-users@lists.basho.com http://lists.basho.com/mailman/listinfo/riak-users_lists.basho.com
