Systems | Development | Analytics | API | Testing

Today we're announcing Kong Operator 2.3. Building on 2.2's expansion into supporting Event Gateway and Dev Portal, this release significantly broadens our feature set. While 2.2 introduced foundational event-driven capabilities, 2.3 brings Kong **AI Gateway** fully into the Kubernetes-native fold, enabling teams to manage LLM routing and policies through familiar GitOps workflows. This update also rounds out Gateway API coverage with `TCPRoute`, `UDPRoute`, and `GRPCRoute`.

AI agents are getting remarkably good at fixing code. Give an agent a well-defined performance problem, enough runtime data, and access to the relevant codebase, and it can often trace the evidence back to a function, suggest an optimization, validate the change, and produce a useful patch. That workflow is no longer particularly difficult to imagine. In some cases, it is already practical. Production debugging, however, has never been only about fixing the code directly in front of you.

Grape handles exceptions with rescue_from blocks declared on your API class: rescue_from :all catches every exception, while rescue_from ActiveRecord::RecordNotFound targets one class. Inside an endpoint, error!("Not Found", 404) halts with a formatted error, defaulting to status 500. Without a handler, invalid params return 400 and other exceptions bubble up to Rack. This guide covers Grape 3.3. Every response body, status code, and error message was verified on Grape 3.3.5, Rack 3.2.7, and Ruby 3.4.10.

You can now ask your coding agent to set up AppSignal in your application. Give it a prompt, let it follow the installation instructions, and watch a checklist fill in as data starts arriving. Installing AppSignal was already straightforward, but it still meant checking your environment, adding the right integration, creating an app, handling credentials, and confirming that telemetry arrived. These are useful checks, but they don't all need your attention.

In the life sciences industry, where breakthroughs in research and healthcare are fueled by data, data silos can be a big problem. Data silos might be caused by things like legacy systems, departmental divisions, disparate data formats, or lack of interoperability standards. Data silos can manifest at any point in the product lifecycle and make it hard for the right people to access and use the information they need, when they need it.

At Insomnia, we believe your tools should support you (and your agents!), not force you into certain ways of working. Over the last few months, we’ve been hard at work streamlining our interface so that it’s easier than ever for you to get started, stay organized, and work however you want with your APIs. There are two key concepts when a developer works with an API.