---
title: Frequently asked questions
description: Find answers to frequently asked questions about Honeybadger's Ruby gem for error tracking and application monitoring.
url: https://docs.honeybadger.io/lib/ruby/support/faq/
---

## Why aren’t my errors being reported?

The most common reason for errors not being reported is that the gem is in a development environment. See the [Environments](https://docs.honeybadger.io/lib/ruby/errors/environments/#development-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](https://docs.honeybadger.io/lib/ruby/errors/ignoring-errors/#ignore-by-class).

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](https://docs.honeybadger.io/lib/ruby/support/troubleshooting/#my-errors-arent-being-reported).

## Why aren’t I getting notifications?

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.

## Can I use Honeybadger outside of Rails, such as in my gem?

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](https://docs.honeybadger.io/lib/ruby/getting-started/plain-ruby-mode/).

See the [API Reference](https://www.rubydoc.info/gems/honeybadger/Honeybadger/Agent) for all the methods you can use to report errors from anywhere in Ruby.

## After enabling Insights, I see a lot of extra console output during my builds. How can I silence this?

If you enabled Insights via your `config/honeybadger.yml` file, you may see extra output in your console during builds (such as asset compile in Docker). This is because the Honeybadger Insights agent is running as configured. You can temporarily disable Insights during your builds by setting the `HONEYBADGER_INSIGHTS_ENABLED` environment variable to `false`.

```bash
HONEYBADGER_INSIGHTS_ENABLED=false bundle exec rake assets:precompile
```

Alternatively, instead of configuring Insights in your `config/honeybadger.yml` file, you can enable it via the `HONEYBADGER_INSIGHTS_ENABLED` environment variable in your proudction environment. This way, Insights will only be enabled in production.

---

## Try Honeybadger for FREE

Intelligent logging, error tracking, and Just Enough APM™ in one dev-friendly platform. Find and fix problems before users notice.

[Start free trial](https://app.honeybadger.io/users/sign_up)

[See plans and pricing](https://www.honeybadger.io/plans/)