Dev config flags: raise_on_error, log_payload, transmit, logger_level

[waltjones]

Implements the dev flags recently defined for all SDKs.

The verbose flag has already been implemented in this SDK as logger_level, and this remains unchanged. Further, the existing default logger_level setting of :info is retained. Finally, in keeping with the expected way of disabling config settings, setting a falsey value for logger_level disables the verbose logging completely.

Fixes #708
Fixes #813

[ArturMoczulski]

@waltjones what do you think about adding verbose as an alias for logger_level to remain the standard across SDKs?

[tisba]

I found this PR by accident.

I was wondering why the config generator does not mention these options, nor does the official documentation at https://docs.rollbar.com/docs/ruby.

I'm trying to figure out, how I can log everything in dev to the application log in development, without sending data to Rollbar. Can someone give me a hint? Thanks!

[waltjones]

@tisba Yes, the docs and the generator are out of date. I've opened #948 to track this.

I think the config options you want are:

config.enabled = true
config.transmit = false
config.log_payload = true
config.logger = your_logger # e.g. Rails.logger
config.logger_level = level # :debug, :info, :warn, or :error

[tisba]

That does not seem to work.

If I make these adjustments (using logger_level = :debug, I get this:

Rollbar.error("this is a test", foo: "bar")

returns "disabled" and nothing gets logged.

[joeesteves]

It seems an access_token is always required .. even for logging

rollbar-gem/lib/rollbar/notifier.rb

Line 203 in c1a2a00

def enabled?