Feature request: disable logging in development if Rollbar is disabled

[allspiritseve]

I have rollbar disabled in development, but any time there's an exception I get log messages like this:

[Rollbar] Reporting exception: undefined method `submissions' for nil:NilClass
[Rollbar] Exception not reported because Rollbar is disabled

It would be nice if there was a way to disable these as they clutter up my log file and are unnecessary if Rollbar is disabled.

[brianr]

Makes sense. Probably the way to do this is to implement a dummy object that can stand in as config.logger, and have an easy way to tell Rollbar to use it instead of the rails logger.

[allspiritseve]

It doesn't look like the code is even using config.logger:

https://github.com/rollbar/rollbar-gem/blob/master/lib/rollbar/exception_reporter.rb#L23-L29

I think the ideal solution would be requiring Rollbar to be included as Rack/Rails middleware in config/environments/*.rb or config/application.rb, so it just doesn't even get run in environments where it is disabled (Oink is an example of a gem that does this).

However, if there's a way to disable the logging in the configuration, that would be an acceptable compromise :)

[brianr]

Oh, good find; that should be using Rollbar.logger:

https://github.com/rollbar/rollbar-gem/blob/master/lib/rollbar.rb#L236-L242

(which also shouldn't be private).

[grosser]

👍

[kritik]

+1 waiting for this feature. And I would also like to disable posting dev data even if Rollbar is enabled

[tisba]

Any news on this one? I actually would like to disable (or redirect) Rollbar logging in production as well (even if Rollbar reporting is enabled).

We are logging JSON-lines to be processed with Logstash. Rollbar's logging is quite annoying and messes up the logs.

[jondeandres]

@tisba we didn't work on this yet, but you could always set config.logger to an instance of NullLogger like this one, https://github.com/rack/rack/blob/master/lib/rack/nulllogger.rb.

So depending on the environment you are, you can set that logger or not. We'll try to find a configuration solution for this or perhaps adding or not the middleware to the stack.

[tamvm]

Any progress for this issue? It's still open for long time

[fagiani]

Bump! any hope for this?