We're excited to announce the general availability of Konnect Debugger, formerly known as Active Tracing during its tech preview phase. This powerful debugging and observability solution in Kong Konnect has evolved from a focused tracing tool into a comprehensive debugging platform.
Konnect Debugger retains all the great capabilities you loved from Active Tracing while expanding to provide unprecedented visibility into API traffic, now combining detailed tracing and comprehensive logging to empower you to optimize performance, troubleshoot issues, and refine your API strategies with confidence.
Intermittent service issues can be elusive and challenging to understand. To ensure optimal performance and reliability, it’s essential to have a clear view into your service’s behavior. This is where comprehensive observability comes in — providing the ability to understand and contextualize system behavior even in the absence of known issues.
When critical services malfunction, pinpointing the root cause can be daunting. Is it a DNS issue, an upstream service anomaly, undetected failures, or a gateway problem? For platform operation teams, accessing component-level data and detailed logs is crucial for rapid mean time to resolution (MTTR).
However, generating and storing detailed telemetry data and logs continuously may be detrimental to the performance of the service and unnecessary. This is where targeted, on-demand insights become invaluable — enabling teams to swiftly identify and resolve issues, minimizing service disruptions.
Building on the foundation of Active Tracing's powerful targeted tracing capabilities, Konnect Debugger represents the natural evolution of our observability offering. All the features you relied on in Active Tracing remain intact and enhanced:
What's new is the expanded scope: Konnect Debugger now combines these proven tracing capabilities with comprehensive logging, giving you a complete debugging solution in a single, integrated interface.
With Konnect Debugger, infrastructure administrators can initiate targeted debugging sessions in specific API gateway nodes. During a debugging session, the selected gateway generates both detailed OpenTelemetry-compatible traces and comprehensive logs for all requests matching the sampling criteria. The detailed spans and log entries are captured for the entire request/response lifecycle. These traces and logs can be visualized with Konnect’s built-in debugging interface with no additional instrumentation or telemetry tools. Konnect’s Debugger offers exclusive, in-depth insights that can't be replicated by third-party observability tools.
By capturing detailed, component-level telemetry data and logs, platform operations teams can gain a deeper understanding of their services’ performance, dependencies, error conditions and potential bottlenecks. This targeted approach to observability enables teams to optimize their services, reduce uncertainty, and improve overall system reliability.
Traces and logs captured in a Konnect Debugger session can be visualized in Konnect's built-in debugging interface. The debugger provides a summary view, trace view, and logs view. You can gain instant insights with the summary view, dive deeper with the trace view, and examine detailed execution logs for comprehensive troubleshooting.
Summary view helps you visualize the entire API request-response flow in a single glance. This view provides a concise overview of critical metrics, error indicators, and a transaction map. The transaction map includes the plugins executed by Kong on both the request and the response, along with the times spent in each phase. Use summary view to quickly understand the end-to-end API flow, identify performance bottlenecks, spot errors, and optimize your API strategy.
The trace view gives you unparalleled visibility into Kong's internal workings. This detailed view breaks down into individual spans, providing a comprehensive understanding of:
Use trace view to troubleshoot issues, optimize performance, and refine your configuration with precision.
The logs view provides comprehensive logging information captured during the debugging session. This detailed view includes:
Use logs view to investigate specific execution paths, understand error conditions, and gain detailed insights into request processing behavior.
We're excited to see how Konnect Debugger will enhance your API operations! Get started with Konnect Debugger today and unlock comprehensive insights into your API traffic.
If you're a Kong Konnect customer, Debugger is now available for your organization. [Log in](https://cloud.konghq.com/login)Log in to Konnect, navigate to the gateway manager, select a control plane, and start debugging your APIs with both traces and logs. If you're new to Kong, you can start by [signing up for Kong Konnect](https://konghq.com/products/kong-konnect/register)signing up for Kong Konnect for free!
Be sure to share your feedback with us. Your input helps us continue to improve this powerful debugging solution.
APIs are the lifeblood of disruption . . . when leveraged correctly. The best, most disruptive businesses are able to harness API growth as a strategic opportunity. But how? With an API platform that drives innovation, faster delivery, and top-tier
[](https://konghq.com/blog/product-releases/new-enhancements-to-konnect)
Managed Redis cache is a turnkey "Shared State" add-on for Kong Dedicated Cloud Gateways. It is designed to combine the performance of an in-memory data store with the simplicity of a SaaS product. When you spin up a Dedicated Cloud Gateway in Kong
[](https://konghq.com/blog/product-releases/multicloud-cloud-gateways-managed-redis-cache)
With Kong Ingress Controller, when your Control Plane was hosted in Kong Konnect, and you were using Kubernetes Gateway API, your dataplane, routes, and services were in read-only mode. When using Kong Ingress Controller with Kubernetes Gateway API
[](https://konghq.com/blog/product-releases/kong-operator-2-1)
The Kong MCP Registry acts as a central directory for AI agents and clients to access services that provide context or take action. For AI agents, think of it as a combination of a "Service Catalog" and a "Developer Portal." It offers the metadata,
[](https://konghq.com/blog/product-releases/kong-mcp-registry-tech-preview)
We've talked about why 2026 is the year of AI unit economics . There, we explored the "2025 hangover" where organizations realized that without financial governance, AI isn't just a science project but has become a margin-bleeding cost center. But
[](https://konghq.com/blog/product-releases/konnect-metering-and-billing-demo)
If you've used KAi before, you'll notice the difference immediately. The enhanced version has deeper access to your Konnect environment and new tools for debugging, analytics, and configuration management: Active tracing and debugging: KAi can now
[](https://konghq.com/blog/product-releases/kai-upgrade-powered-by-konnect-mcp-server)
Every January, the same resolutions show up: eat better, exercise more, finally learn that language, finally figure out that production use case for AI agents (OK, this one isn’t so typical unless you operate in our universe). But if you're respons
[](https://konghq.com/blog/product-releases/ai-cost-control)