Be sure to replace ```POST_SERVER_ITEM_ACCESS_TOKEN``` with your project's ```post_server_item``` access token, which you can find in the Rollbar.com interface.

The above will configure rollbar to catch and report all exceptions that occur in your Pyramid app. However, if there are any middlewareapplications that wrap your app, Rollbar will not be able to catch exceptions.

In order to catch exceptions from Pyramid and middleware code, you will need to create a ```pipeline``` where the rollbar middleware wraps your Pyramid app.

</dd> <dt>environment</dt> <dd>Environment name. Any string up to 255 chars is OK. For best results, use "production" for your production environment. </dd> <dt>exception_level_filters</dt> <dd>List of tuples in the form ```(class, level)``` where ```class``` is an Exception class you want to always filter to the respective ```level```. Any subclasses of the given ```class``` will also be matched.

</dd> <dt>timeout</dt> <dd>Timeout for any HTTP requests made to the Rollbar API (in seconds).

Default: ```3```

</dd> <dt>allow_logging_basic_config</dt> <dd>When True, ```logging.basicConfig()``` will be called to set up the logging system. Set to False to skip this call. If using Flask, you'll want to set to ```False```. If using Pyramid or Django, ```True``` should be fine.

Default: ```True```

</dd> </dl>

## Help / Support

If you run into any issues, please email us at [support@rollbar.com](mailto:support@rollbar.com)

You can also find us in IRC: [#rollbar on chat.freenode.net](irc://chat.freenode.net/rollbar)

For bug reports, please [open an issue on GitHub](https://github.com/rollbar/pyrollbar/issues/new)