You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following config options are independent of each other:
enabled
* Enable or disable Rollbar in your project. This can be changed at runtime with Rollbar::enable() and Rollbar::disable() or through Rollbar::configure().
* If this is false then do absolutely nothing, try to be as close to the scenario where Rollbar did not exist at all in the code.
* Default: true
NOTE: This option is already implemented sometime ago. Verify its implementation logic to be consistent with other SDKs...
transmit #163
* Should the SDK actually perform HTTP requests to Rollbar API. This is useful if you are trying to run Rollbar in dry run mode for development or tests.
* If this is false then we do all of the report processing except make the post request at the end of the pipeline.
* Default: true
logPayload #164
* Log the payload body to the configured logPayloadFile (default: "rollbar.payloads").
* If this is true then we output the payload to standard out or a configured logger right before transmitting.
* Default: false
verbose (or verbosity) #???
* This configuration option controls the verbosity of the internal logs of the SDK.
* The value is one of the following with an increasing level of verbosity:
* The levels should follow: https://tools.ietf.org/html/rfc5424
* Additionally, there will be none level which makes the SDK quiet.
* Default: none
The defaults could be environment-dependent and we would just need to work out what those should be.
The text was updated successfully, but these errors were encountered:
The following config options are independent of each other:
enabled
* Enable or disable Rollbar in your project. This can be changed at runtime with Rollbar::enable() and Rollbar::disable() or through Rollbar::configure().
* If this is false then do absolutely nothing, try to be as close to the scenario where Rollbar did not exist at all in the code.
* Default: true
NOTE: This option is already implemented sometime ago. Verify its implementation logic to be consistent with other SDKs...
transmit #163
* Should the SDK actually perform HTTP requests to Rollbar API. This is useful if you are trying to run Rollbar in dry run mode for development or tests.
* If this is false then we do all of the report processing except make the post request at the end of the pipeline.
* Default: true
logPayload #164
* Log the payload body to the configured logPayloadFile (default: "rollbar.payloads").
* If this is true then we output the payload to standard out or a configured logger right before transmitting.
* Default: false
verbose (or verbosity) #???
* This configuration option controls the verbosity of the internal logs of the SDK.
* The value is one of the following with an increasing level of verbosity:
* The levels should follow: https://tools.ietf.org/html/rfc5424
* Additionally, there will be none level which makes the SDK quiet.
* Default: none
The defaults could be environment-dependent and we would just need to work out what those should be.
The text was updated successfully, but these errors were encountered: