Honeybadger now integrates with Oban (the Python port of the Elixir background job library).
With this release you can report unhandled worker exceptions and emit per-job telemetry to Honeybadger Insights.
We now support detailed issue exports to third-party managers. When enabled, your issue exports to GitHub or GitLab will contain the full markdown, or the full Jira wiki for JIRA Cloud and JIRA Server, giving you and your team all the information you need to solve errors.
If you need to keep your Insights data longer than Honeybadger stores it, Business and Enterprise accounts can now replicate data to third-party archive destinations such as Amazon S3 or Cloudflare R2.
Insights dashboard widgets can now reference dashboard-level parameters in their queries. This enables you to reuse the same dashboard for different hosts, environments, customers, or other values without reconfiguring each widget individually.
Want to make sure a teammate sees an issue? When adding comments to errors, you can now tag other project members by typing “@” and completing the user’s name.
Honeybadger is now available on AWS Marketplace, so you can subscribe with your AWS account and pay for Honeybadger on your existing AWS bill. Usage is metered hourly.
Changing authenticator apps no longer requires disabling 2FA first. You can now configure your new authenticator app directly from your account settings while your account stays protected during the process.
Honeybadger Insights is now available in our Go client library. Send structured events, query them with BadgerQL, and build monitoring dashboards in the same tool you use for error monitoring.
When Honeybadger creates a GitHub issue for an error, you can now specify an issue type so issues land in your GitHub workflow already categorized.
Honeybadger now integrates with Backlog. When errors occur, Honeybadger automatically creates issues in your Backlog project and keeps status in sync as errors are resolved or reopened.