Closed elblivion closed 7 years ago
👋 Hmm... I know logAll
will get set to true
if a logger is set when the backend is initialized. Could that be what you are seeing? https://github.com/librato/statsd-librato-backend/blob/master/lib/librato.js#L467-L471
~We should definitely get this documented since our README makes no mention of it. cc @niklibrato~ config.debug
is actually a statsd config option. Maybe we still document it?
I'm not really proficient in Javascript, but that seems to be the case. What should we do if we want to not logAll
?
It seems like we should honor config.debug
, regardless if you have a statsd logger configured or not. The alternative is to remove your logger from your statsd instance which...isn't ideal.
I'll get a PR opened to fix this.
Thanks!
Hi,
We're deploying statsd in Kubernetes, and logging to stdout. We currently get everything in our logs, including "DEBUG" messages, e.g. https://github.com/librato/statsd-librato-backend/blob/master/lib/librato.js#L64-L66.
Our config does not set the
debug
value in statsd, it seems something is forcing thislogAll
to be true - could you please help us out?Thanks!