Systems | Development | Analytics | API | Testing

Debugger in Kong Konnect

Are you spending too much time trying to track down failing requests or figure out performance issues within your Kong API Gateway? In this quick demo, we show you how to use Konnect's Debugger to save hours of debugging time by rapidly finding the root cause of latency and other issues. You'll learn how Debugger allows you to set up deep tracing sessions for your Kong data planes, collecting OpenTelemetry-compatible traces across the entire request and response lifecycle. We will walk you through a real-world scenario where we diagnose a spike in latency for a specific service.

Introducing Konnect Debugger: Get Unprecedented API Traffic Visibility

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.

Beyond console.log: Smarter Debugging with Modern JavaScript Tooling

Ask any JavaScript developer their most used debugging tool and chances are the answer will be console.log. It’s immediate, low friction, and available in every browser. For development, it’s fantastic. But for production and complex applications, if you rely on console.log alone, cracks begin to show. It lacks context, doesn’t persist, and makes reproducing or analyzing user-reported issues a challenge. In this article, we’ll look at smarter, scalable debugging strategies.

Unlocking AI: Auto-Documentation & Debugging for Distributed Systems

AI is everywhere. Depending on who you ask, it’s either making developers obsolete, or it’s just hype. But for those of us who’ve actually used AI tools in real-world engineering workflows, especially in complex distributed systems, the truth lies somewhere in between. At Multiplayer, we’ve spent the past few years exploring how AI can—and can’t—help solve two of the most persistent challenges in distributed systems: documentation and debugging.

How to Use Playwright Trace Viewer for Faster Debugging?

Three years ago, I discovered Playwright Trace Viewer while helping our team debug a complex audio processing application. What started as curiosity became a game-changer that now saves us hours every week. We had this complex flow where users could upload audio files, apply effects, and export them. Screenshots were our go-to debugging tool, until they weren't. One day, a test kept failing in CI. The screenshot showed everything looked perfect.

Testing Vs Debugging: Prioritize Efficiently

In the world of software development, testing and debugging are two of the key components. These two key components are dedicated to different purposes. Before you prioritize between these two and know more about testing vs. debugging, you must have an in-depth knowledge of testing individually. Testing and debugging are essential for software development projects. This write-up will break down these two components, and you will receive insight into the comparisons and the factors related to them.

PHP 8.4 improves Closure Naming for simplified debugging

In applications that use closures excessively, understanding stack traces as part of the debugging experience has historically been complicated by the fact that the names of closures did not include the source location. In a PHP stack trace, whenever a frame was represented by a closure, it only contained the reference {closure} and the namespace the closure was declared in, leading to all closures within a namespace looking identical.