The Honeybadger Changelog

Debugging errors is faster when your AI assistant has full context about what's happening in your application. We just released honeybadger-mcp-server, a new Model Context Protocol (MCP) server that provides AI tools—such as Claude, Cursor, and Copilot—with direct access to your Honeybadger error data and project information.

Automatically fixing a Honeybadger error in Cursor

The MCP server automatically connects your development environment to Honeybadger's API, enabling your AI assistant to manage your Honeybadger projects, retrieve detailed error information and affected user data, access occurrence counts and project reports, and query specific errors with their full context for real-time debugging.

How it works

The MCP server acts as a bridge between Honeybadger's API and MCP-compatible AI tools. Instead of manually copying error details or switching between tools, your AI assistant can directly fetch relevant error information, analyze patterns, and provide contextual debugging suggestions—all within your existing workflow.

Getting started

1. Pull the Docker image:

   docker pull ghcr.io/honeybadger-io/honeybadger-mcp-server:latest
   

2. Get your personal auth token from your Honeybadger User settings under the "Authentication" tab

3. Configure your dev environment to run the MCP server (supports Claude Desktop, Cursor, Windsurf, VS Code, Zed, and more)

4. Start debugging faster with your Honeybadger-aware code assistant

Beta release and roadmap

This is a beta release focused on error tracking and project management—but even with those two features, honeybadger-mcp-server is surprisingly capable. We're actively developing additional tools for working with Honeybadger Insights data, account and team management, uptime monitoring, and other platform features. More to come!

Check out the honeybadger-mcp-server docs for detailed setup instructions for your specific development environment.

Coordinating your incident response across multiple tools during a system outage can waste precious time. To help you move faster, we've integrated Honeybadger with Rootly. Rootly is an incident management platform that automates response workflows directly in Slack and other team communication tools.

Our integration automatically creates alerts in Rootly based on events from across your Honeybadger monitoring stack:

• Error Tracking: New errors and error rate spikes
• Uptime Monitoring: Site outages, recoveries, and SSL expiration warnings
• Cron & Heartbeat Monitoring: Failed or missing scheduled jobs
• Insights Alarms: Custom alerts from Honeybadger Insights

A Honeybadger alert in Rootly

From there, use Rootly's automated alert workflows to create and manage incidents with Honeybadger's rich diagnostic data.

How it works

Honeybadger sends events to Rootly via secure webhooks, automatically creating alerts with direct links back to Honeybadger for deeper investigation. We include detailed contextual data with each event that you can use to customize Rootly's alert workflows for your specific needs—whether that's automatically creating incidents for critical errors, routing alerts to particular teams, or triggering custom automations based on the type of issue detected.

When Rootly receives an alert from Honeybadger, you can manually declare an incident or configure Rootly's alert workflows to create incidents based on specific criteria automatically. Once an incident is created, Rootly takes over the orchestration—spinning up dedicated Slack channels, looping in the right responders, creating Zoom rooms, and providing step-by-step guidance for incident response.

Sending Honeybadger alerts to Rootly

Here's how to configure the integration:

1. Navigate to your project's Settings → Alerts & Integrations page
2. Select Rootly under "Add a project integration"
3. In Rootly, create a Generic Webhook alert source named "Honeybadger" and copy the authorization token
4. Paste the webhook token into Honeybadger's integration settings
5. Optionally specify a target type and target ID for routing alerts
6. Save and test the integration to send a sample event to Rootly

As a final step, you'll need to configure the Alert Content settings for your Rootly webhook alert source using these template variables:

• Alert Title: {{ alert.data.title }}
• Alert Description: {{ alert.data.description }}
• Link to Alert: {{ alert.data.url }}

Honeybadger's Rootly integration is available for all Honeybadger accounts. Check out our Rootly integration docs for detailed setup instructions.

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 automatic 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.

When incidents strike, every second counts. That's why we're excited to announce a new integration with incident.io, the modern incident management platform that helps teams resolve production issues faster—just like Honeybadger!

Once enabled, Honeybadger will automatically create and resolve alerts in incident.io based on events from your Honeybadger projects, including:

• Error Tracking: New errors and error rate spikes
• Uptime Monitoring: Site outages and recoveries
• Cron & Heartbeat Monitoring: Missing or reporting check-ins
• Insights Alarms: Custom alerts from your BadgerQL queries

A Honeybadger error notification in incident.io

How it works

We use incident.io's alert sources to intelligently deduplicate events, ensuring your team isn't overwhelmed by duplicate alerts. When an issue is resolved in Honeybadger, we automatically resolve the corresponding alert in incident.io, keeping your incident status accurate without requiring manual updates.

Each alert includes:

• A descriptive title with the issue details
• Direct links back to Honeybadger for investigation and resolution
• Smart deduplication keys to prevent alert fatigue
• Contextual metadata about the source of the issue

Getting started

Setting up the integration is simple:

1. Navigate to your project's Settings → Alerts & integrations page
2. Select incident.io under "Add a project integration"
3. Create an API key in incident.io with these permissions:
   • Create incidents
   • Edit incidents
   • Create and manage on-call resources
4. Enter your incident.io API key in Honeybadger
5. Give your alert source a descriptive name
6. Save and test the integration

Honeybadger will automatically create and configure the alert source in incident.io for you without any manual setup required on their end.

This integration is available immediately for all Honeybadger accounts. For more details on configuring incident.io alerts, check out our integration docs.

Teams using Zulip for team chat can now receive Honeybadger alerts directly in their Zulip channels. Zulip's unique topic-based threading makes it easy to keep error discussions organized and accessible, even across different time zones and async work schedules.

Honeybadger's integration automatically sends notifications to your configured Zulip channel and topic, including:

• Error Tracking: New errors and error rate spikes
• Uptime Monitoring: Site outages, recoveries, and SSL expiration warnings
• Cron & Heartbeat Monitoring: Missing scheduled jobs and check-ins
• Insights Alarms: Custom alerts from Honeybadger Insights

Honeybadger generates formatted messages that include essential details about each event, such as project name, environment, revision information, and direct links to the Honeybadger dashboard for rapid troubleshooting and resolution. The integration uses Zulip's incoming webhook bot feature to deliver messages to your team's topics and channels:

A Honeybadger error notification in Zulip

How to integrate Zulip with Honeybadger

1. In your Zulip organization, go to Settings → Bots and create a new Incoming Webhook Bot
2. Copy the bot's email address and API key
3. In Honeybadger, navigate to your project's Settings → Alerts & integrations page
4. Select Zulip from the list below "Add a project integration"
5. Fill in your Zulip domain and bot credentials, and specify which channel and topic should receive alerts
6. Choose which notification types you want to receive and save the integration

You can test the setup using the "Test this integration" button to ensure everything works before going live.

The new Zulip integration is available immediately for all Honeybadger accounts. Check out our Zulip integration docs for detailed setup instructions.

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.