Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider moving logging over to lager. [JIRA: RIAK-1918] #169

Open
evanmcc opened this issue May 27, 2014 · 1 comment
Open

Consider moving logging over to lager. [JIRA: RIAK-1918] #169

evanmcc opened this issue May 27, 2014 · 1 comment

Comments

@evanmcc
Copy link
Contributor

evanmcc commented May 27, 2014

Because we're getting filtered/rate-limited in certain situations (see error messages in basho/riak#517), and backpressure might serve us better. Lager is already a dep, so maybe might as well use it? Or perhaps a logging macro, so the user can decide at compile time which system they'd like to use.

@evanmcc evanmcc added this to the 2.1 milestone May 27, 2014
@bsparrow435
Copy link
Contributor

This has been requested by customers as well so that all common logs(such as bitcask merge messages) can be easily groked with logstash and other 3rd party tools. The lager built in formatter if very nice for this functionality

@Basho-JIRA Basho-JIRA changed the title Consider moving logging over to lager. Consider moving logging over to lager. [JIRA: RIAK-1918] Jul 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants