Operations | Monitoring | ITSM | DevOps | Cloud

We just added two new AI features to our app: natural-language translation for Error search and Insights queries. Honeybadger has two query languages: Error search speaks a simple token syntax in the spirit of Solr or a basic Elasticsearch query, while Insights runs on BadgerQL (BQL), our own language for digging into your event data, designed to feel familiar to CloudWatch Insights and Splunk users. Both are powerful, but sometimes you just want something that works without having to open up the docs.

Deployment is not the end of shipping your application. From time to time, you will get errors that you will need to attend to. Without a good method of catching errors or logs in general, you could end up with uncaught issues that might cost you valuable customers in the process. In this article, you will learn how to catch logs for an application deployed on Fly.io. You will learn how Fly.io logging works, then learn ways to handle logs natively on the platform.

Your MCP client doesn’t need your whole API key just to look up an error anymore. Honeybadger's hosted MCP server now supports OAuth. You can approve it through your browser, scope your permissions, revoke your permissions, and rest easy knowing that our tokens auto-refresh and don’t sit around in a config. Keep reading to see how it works and get a quick recap of everything else that shipped this cycle.