Instantly know when Rails errors occur and how to fix them
Rails errors are tracked by Rollbar instantly as they occur. Get notified of errors and how to fix them throughout the software development process.
Similar Rails errors are automatically grouped using Rollbar's fingerprinting technology to reduce noise, and all errors include detailed data to help you assess impact and assign priority.
Rollbar automatically collects all the data you need to replicate and debug a Rails error, presented in ways optimized for debugging speed.
Get stack traces, request parameters, local variables, affected users and IP addresses, browsers and OSes, deployed code versions, and more.
RQL (Rollbar Query Language) allows you to perform data analysis and build custom reports on your Rails error data, using a familiar SQL-like language.
You can use RQL to get answers to very specific questions, e.g. "How many users are getting by 404 errors right now, grouped by referring URLs?"
RQL is also accessible via API.
Rollbar supports all popular languages and frameworks:
Using Rollbar I don’t have to spend time trying to reproduce errors on my own. It tells me what the steps are. Rollbar empowers your team to be able to sort through issues and turn things around quickly.
How to configure rollbar-gem to work with your Rails app
Run the following command from your Rails root:rails generate rollbar POST_SERVER_ITEM_ACCESS_TOKEN
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.
14-day unlimited errors free trial. 5,000 errors/month free forever.
Usage
Uncaught exceptions in Rails controllers will be automatically reported to Rollbar. You can use one of Rollbar.log(level, ...)
, Rollbar.debug()
, Rollbar.info()
,Rollbar.warning()
, Rollbar.error()
and Rollbar.critical()
to report caught exceptions and messages.
The methods accept any number of arguments. The last exception is used as the reported exception, the last string is used as the message/description, and the last hash is used as the extra data...