The Honeybadger Changelog

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 timestamp of the current query to around the time of the event. This is very useful to get a gage of all events that happened during a timeframe without needing to input 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 for you: 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 then Insights doesn't need to scan that data when executing your query. So for example, if you're just 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.

You can now send events to Honeybadger Insights from our Elixir client library. Use the Honeybadger.event/1 function to send event data to the events API. A ts field with the current timestamp will be added to the data if it isn't provided:

Honeybadger.event(%{
  event_type: "user_created",
  user: user.id
})

You can also use Honeybadger.event/2, which accepts a string as the first parameter and adds that value to the event_type field in the map before being sent to the API:

Honeybadger.event("user_created", %{
  user: user.id
})

You can find these events with the following BadgerQL query:

fields @ts, @preview
| filter event_type::str == "user_created"
| sort @ts

This is just the first step towards supporting logging and performance monitoring in Elixir!