Frequently Asked Questions
The most common reason for errors not being reported is that the gem is in a development environment. See the Environments chapter in the Getting Started guide for more information.
The second most common reason is that the error being reported is on the default ignored exceptions list.
We also don't capture errors in a Ruby console (IRB, pry, etc..) by default, even in production.
If neither of these is the issue, check out the Troubleshooting guide.
By default we only send notifications the first time an exception happens, and when it re-occurs after being marked resolved. If an exception happens 100 times, but was never resolved you'll only get 1 email about it.
Yes! All our gem needs to report errors is a supported Ruby version; there are no other hard dependencies. We detect and integrate with optional dependencies such as Rails by default, but if you want complete control of the initialization process you can use Plain Ruby Mode.
See the API Reference for all the methods you can use to report errors from anywhere in Ruby.