The Honeybadger Changelog

Here's what's cooking at Honeybadger.

Export error data as Markdown

You can now export your error details and stack traces as Markdown files—useful for creating documentation, sharing with team members who don't have Honeybadger access, or integrating with AI-workflows.

Export dropdown menu showing options: Download as Markdown, Copy Markdown to clipboard, Send details for all occurrences via email

Here's how to export an error as Markdown:

  1. Navigate to any error in your project dashboard
  2. Click the Export dropdown in the error actions panel
  3. Select Download as Markdown from the dropdown menu

The .md file download includes the error summary, stack trace, environment details, and breadcrumbs formatted in standard Markdown syntax compatible with GitHub, Notion, Google Docs, and other Markdown-capable tools.

Learn more about error monitoring →

Require multi-factor authentication for your team

Account owners can now require multi-factor authentication (also known as two-factor authentication, 2FA, or MFA) for all users—useful for compliance and to improve account security.

MFA requirement interface showing notification "All account users must have MFA enabled to access this account" with Disable MFA Requirement button, Compliance Status at 100% compliant, and Users Requiring MFA section confirming all users have MFA enabled

Here's how to configure it:

  1. Navigate to Settings & billing → Authentication in account settings
  2. Click Enable MFA Requirement in the Require MFA section

Honeybadger supports two-factor authenticator apps such as Authy, Google Authenticator, and 1Password.

When you require multi-factor authentication, we'll notify the users who need to set it up via email, and prompt them to enable it on their next login.

See the Honeybadger docs to learn more about managing users in Honeybadger.

Customizable timeouts for uptime checks

We're excited to announce a new timeout configuration option for uptime checks! This feature gives you more control over how long your uptime checks wait for responses from your endpoints.

With a custom timeout value for each uptime check, you can:

  • Increase the timeout (up to 120 seconds) for endpoints that naturally take longer to respond (e.g., database-heavy operations)
  • Decrease the timeout (down to 1 second) to enforce strict SLA requirements (e.g., ensuring responses within 5 seconds)

When an uptime check exceeds your configured timeout, it will be marked as failed, helping you identify performance issues that don't meet your requirements.

This feature is available now on Business and Enterprise tiers. Other tiers will continue to use the default timeout of 30 seconds.

To configure timeout settings for your uptime checks:

  1. Navigate to your uptime check settings
  2. Look for the new "Timeout" field
  3. Set your desired timeout value (in seconds)
  4. Save your changes

The timeout configuration will take effect immediately for new check runs.

Link existing Linear issues to errors in Honeybadger

The Linear integration can now link Honeybadger errors to existing Linear issues—useful for preventing duplicate issues when an error corresponds to work that's already in progress.

When viewing an error in Honeybadger, here's how to link it to an existing Linear issue:

  1. Navigate to the error page in your Honeybadger project
  2. Click the dropdown arrow next to Create issue in the error actions
  3. Select Link existing issue to open a search dialog
  4. Search for your Linear issue by number or title

Honeybadger searches within your configured Linear project and displays matching issues with their titles and issue numbers.

Once linked, you can jump to the Linear issue directly from the error actions, and (when enabled) Honeybadger will keep the error status in sync when you close or re-open the issue.

Learn more about the Linear integration →

Earn free monitoring credits with our new customer referral program

Your clients and coworkers are already asking about Honeybadger when they see how smoothly your apps run. Now when they sign up, you can earn credits towards your own account.

Our new customer referral program gives you up to 20% of referred revenue as credit towards your bill. Refer a company paying $200/month and earn up to $40/month in credits—enough to cover a full $26/month team account with room to grow.

When you join:

  • Share your unique referral link with colleagues and coworkers
  • Earn up to 20% of referred payments as monthly/annual invoice credits
  • Reduce your bill to $0 with enough referrals

Monthly credits apply as long as both accounts remain active; one workplace referral could cover you indefinitely. Note: Credits don't roll over, so use them each month or lose them.

Getting started

  1. Visit Settings & billing → Referrals in your Honeybadger account
  2. Accept the terms to join the program
  3. Share your unique referral link with colleagues and clients
  4. Earn automatic credits on your next bill when they become paying customers

Available immediately for all Honeybadger accounts. Read the full announcement to learn more.

Send Honeybadger alerts to ClickUp Chat channels

Honeybadger can now send alerts directly to your ClickUp Chat channels—keeping your team informed where they already collaborate on projects and tasks.

Here's how to configure it:

  1. Navigate to Settings → Alerts & integrations in your Honeybadger project
  2. Select ClickUp Chat from the Add a project integration list
  3. Authenticate via OAuth and configure your workspace and channel

The integration supports all Honeybadger alert types including error events, uptime monitoring and check-in events, alarms, and more.

After connecting, notifications appear as markdown-formatted messages in your selected ClickUp Chat channel, with direct links back to Honeybadger for troubleshooting and debugging.

See the ClickUp Chat integration docs to learn more.

Automatic Sidekiq monitoring dashboard

When Sidekiq jobs pile up, you need fast answers. Honeybadger Insights already makes it easy to query your Rails performance data, including Sidekiq performance. But it can be hard to know where to start—until now. We just added a new Sidekiq dashboard to Honeybadger.

Screenshot of a Sidekiq dashboard showing background job monitoring metrics including 136,810 successful jobs and 13,526 failures. The interface displays job counts over time for different worker classes (UnbarableJob, SpamUserJob, SendEmailJob, etc.), job durations averaging around 1.2 seconds, and duration distribution charts, providing comprehensive insights into background job performance and system health.
Honeybadger's Sidekiq monitoring dashboard

The Sidekiq dashboard gives you immediate visibility into your background job performance without any custom configuration, and the charts are a great starting point when investigating slowdowns and other issues. The dashboard automatically captures and visualizes your Sidekiq job performance, including:

  • Job volume: Monitor job counts over time by worker class
  • Performance trends: Visualize performance patterns with job durations and distributions
  • Success/failure metrics: View comprehensive worker statistics with totals and averages
  • Bottlenecks: Spot the 10 slowest job runs with execution details

Monitoring Sidekiq performance in Honeybadger

Honeybadger automatically instruments your Sidekiq jobs when you enable Insights in the Honeybadger Ruby gem. To get started, update to gem version >= 5.11 and enable Insights in your config/honeybadger.yml:

insights:
  enabled: true

Once enabled, select "Sidekiq" from the Ruby automatic dashboard templates in your Honeybadger project.

The new Sidekiq dashboard is available immediately for all Honeybadger accounts. Check out our Ruby gem docs for more details on HB's automatic Rails instrumentation.

Connect your AI code assistant directly to Honeybadger

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.

Screenshot of Cursor code editor using a Claude AI model to help fix a Honeybadger error. The left side shows Ruby code for a GoogleHangoutsChat class, while the right side displays Claude actively investigating a Honeybadger EU error by calling API functions like 'get_fault' and 'list_fault_notices'. Claude is analyzing error details and providing real-time debugging feedback within the Cursor development environment.
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.

AI-ready backtraces in Slack error notifications

When errors happen, your AI coding assistant can only help if it has the context it needs. To give you a hand, Honeybadger now includes full backtraces in Slack error notifications.

The backtrace appears as formatted code in Slack, making it easy to copy/paste or forward to your favorite AI debugging assistant like Cursor, Windsurf, or Copilot. Or, if you use Cursor's Background Agents, you can install their Slack integration to ask Cursor to fix the error without leaving Slack!

Screenshot of a Honeybadger error notification in Slack at 12:24 showing a NoMethodError for an undefined 'charge' method in the Monolith project's production environment. The error occurred on line 103 of the order.rb file in the charge_payment method. Below the error details is a chat interface where someone is asking '@Cursor fix this error' with an option to 'Also send to # alerts', demonstrating how developers can quickly escalate Honeybadger errors for AI-assisted debugging and team notification.

If you already have a Slack integration in Honeybadger, this feature is enabled automatically. Check out our Slack integration docs for more info, and our Working with LLMs guide for best practices and to super charge your AI-development workflow with Honeybadger's Model Context Protocol (MCP) server.

Automate Rootly incidents from Honeybadger alerts

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 AlarmsCustom alerts from Honeybadger Insights

Screenshot of a Honeybadger error notification integrated within Rootly's incident management platform. The alert shows '#bkkQ9b [Ben's Shared Project/test] TestingException: This is a test error generated by Honeybadger' with status indicators including a green 'Resolved' badge, 'High' priority, timestamp showing '7 days ago', duration of '00:02:39', and 'Not noise' classification. On the right side are action buttons for 'View Details', 'Create incident', and additional options. The notification displays Honeybadger's logo alongside Rootly's interface elements.
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.