Troubleshooting

Common issues and workarounds for honeybadger-python are documented here. If you don’t find a solution to your problem here or in our support documentation, email support@honeybadger.io and we’ll assist you!

Before you start troubleshooting

1. Make sure you are on the latest version of honeybadger-python.

All errors are not reported

If no errors are reported (even manually via honeybadger.notify):

1. Is the api_key config option configured?
2. Are you in a development environment?

Some errors are not reported

1. Is the error ignored via config?

Errors are not reported when threads are disabled

By default, Honeybadger reports errors in a separate thread. (In AWS Lambda, force_sync defaults to True unless you set it yourself, so this doesn’t apply there.) When force_sync is False, platforms that disable threading (for example, uWSGI without enable-threads) will not report errors. Either enable threading, or set force_sync to True to report errors in the current thread:

from honeybadger import honeybadger

honeybadger.configure(force_sync=True)

Enabling Honeybadger’s internal logging

Honeybadger logs its own activity (such as failed API requests) to the honeybadger logger. By default, this logger uses logging.NullHandler, so you won’t see any output. To see these logs, add a handler to the honeybadger logger:

import logging

logging.getLogger('honeybadger').addHandler(logging.StreamHandler())

In Django, add a honeybadger logger to your LOGGING setting:

LOGGING = {
    'version': 1,
    'disable_existing_loggers': False,
    'handlers': {
        'console': {
            'class': 'logging.StreamHandler',
        },
    },
    'loggers': {
        'honeybadger': {
            'handlers': ['console'],
            'level': 'DEBUG',
        },
    },
}