The Honeybadger Changelog

Introducing Elixir performance monitoring in Honeybadger!

We've added three new features to Honeybadger Insights:

1. A new Phoenix performance dashboard. Instead of creating a dashboard from scratch, select " Phoenix" from our list of curated monitoring dashboards. The new dashboard allows you to monitor requests, slow controllers, Ecto queries, and more.
2. A new Oban dashboard. We love Oban at Honeybadger and thought it would be the perfect companion to the Phoenix dashboard (the first of many useful dashboards, we hope!). The Oban dashboard gives you a quick overview of your Oban performance, including job counts by status, worker stats, and slow jobs.
3. Elixir & Phoenix performance instrumentation. Our Hex package now automatically sends performance events and metrics (via telemetry) from Phoenix and other popular libraries. The new instrumentation powers your dashboard, but you can also use our query language (BadgerQL) to dig into the data yourself, which creates some exciting possibilities.

To use these features, you'll need to upgrade to version ~> 0.24 of the the honeybadger Hex package and enable a config option in your config.exs:

config :honeybadger,
  insights_enabled: true

Honeybadger automatically instruments the following libraries when they are available:

• Ecto: Database queries
• Plug/Phoenix: HTTP requests
• LiveView: Phoenix LiveView lifecycle events
• Oban: Background job processing
• Absinthe: GraphQL query execution
• Finch: HTTP client requests, often used by other libraries like Req
• Tesla: HTTP client requests

You can also customize the default dashboards and send custom logs and events to Honeybadger — read the full blog post to learn more.

We added Cursor, Windsurf, and Zed to the list of supported local editors in user settings:

Honeybadger's local edits feature lets you configure your local editor settings so that we can display links to open files from the error backtrace, jumping directly to the affected line:

Alarms bridge the gap between data and action, transforming any query into an actionable alert that notifies your team. Honeybadger Insights gives you granular control over monitoring without deploying new instrumentation—write a query, set a threshold, and stay ahead of issues before they impact users.

You can send alerts to Slack, PagerDuty, or any of Honeybadger’s many 3rd-party integrations—giving you incredible flexibility when notifying your team and choosing when and how to respond.

To get started, head over to the new Alarms tab in your Honeybadger project to create your first alarm:

Read our announcement blog post and check out the developer docs to learn more.

Insights Alarms are available on the Business plan.

We added a new "find events with request ID" option to the Insights data context menu for request_id fields. This is especially useful when exploring your application events and you find a request that you want to check out.

Clicking the option replaces the current Insights query with the BadgerQL for finding a set of correlated events for that request:

fields @ts, @preview
| filter request_id::str == "$value"
| sort @ts

We added some options to the Insights data context menu for datetimes where you can constrain the current query's timestamp to around the event's time. This is very useful for gauging all events during a timeframe without inputting the time by hand.

The time picker for Insights queries now accepts dates with millisecond precision, allowing you to filter events with greater accuracy than just seconds.

The time picker displays dates using your localized date and time preferences in user settings by default and switches to an ISO standard format when the date contains milliseconds.

If your company has EU data residency requirements, you can now use all of Honeybadger's powerful application performance monitoring tools with the peace of mind that your customer data resides in the European Union.

We've launched a new dedicated EU Honeybadger region that allows customers to store their application performance monitoring and error tracking data entirely within the EU. This service operates from AWS's eu-central-1 region in Frankfurt, Germany, and is available at eu-app.honeybadger.io.

Accounts within Honeybadger's new EU region are purchased separately, allowing you to choose different tiers depending on your usage between our U.S. and EU regions.

Existing customers can create a new EU account without changing their current U.S. account, and new customers can choose their preferred region during signup.

All Honeybadger accounts come with our standard 30-day free trial, and the pricing is the same across both regions. To get started, sign up for a new Honeybadger EU account.

One of the best ways to get started with Honeybadger Insights is to use it with your existing Honeybadger error tracking data—which we include for free with every error tracking plan.

Sometimes you want to know something about a particular error, how many errors have occurred with a specific bit of context data, what else was happening around the time the error occurred, etc.

To make it easier to answer these questions quickly, we’ve added Insights context menus to the error detail page. When you hover over any Insights-enabled field, you’ll notice that the value is highlighted. Click to open a context menu with common Insights operations for that field.

The menu options change based on the type of data (for example, if it’s a number, you’ll see a count operation). When you select an option it opens the query in Insights, making it easy to explore from there.

View an error in Honeybadger to try it out.

Introducing Laravel performance monitoring in Honeybadger!

We've added two new features just for Laravel developers:

1. A new Laravel performance dashboard. Instead of creating a dashboard from scratch, select “ Laravel” from our list of curated monitoring dashboards. The new dashboard allows you to monitor requests and background jobs, slow requests and queries, and more.
2. Laravel performance instrumentation. Our composer package now automatically sends performance events and metrics from Laravel. The new instrumentation is what powers your dashboard, but you can also use BadgerQL to dig into the data yourself.

To use these features, you'll need to upgrade to version 4.2.x of the honeybadger-laravel composer package and enable a config option in config/honeybadger.php:

  'events' => [
      'enabled' => true
  ]

You can also customize the default dashboard and send your application logs to Honeybadger — read the full blog post to learn more.

Streams are the fundamental data sources in Honeybadger Insights. They serve as the starting point for your queries and represent the data you want to analyze.

When you create a new Honeybadger project, we automatically set up two streams: an Internal stream for your Honeybadger-generated events (like errors, uptime checks, and notifications), and a Default stream for the custom data you send to Honeybadger.

You can select the active streams from the steam selector at the top of the query editor. This affects the data that Insights returns for your queries.

Removing a stream you don't need can improve your query response times because Insights doesn't need to scan that data when executing your query. So, for example, if you're querying your application telemetry, you can remove the Internal stream to get a faster response.

You can’t create additional streams yet, but that’s something we’re considering.

Check out the developer docs to learn more.