Debugging Node.js in Docker and Kubernetes Without Restarting

There's a Node.js service running in a Kubernetes pod. It's slow. You need to figure out why. But you can't SSH into the container. You can't redeploy with --inspect. You can't attach a debugger the way you would on your laptop. This is the reality of debugging in containerized environments. The tools that work perfectly in development — Chrome DevTools, node --inspect, clinic.js — all assume you have direct access to the machine running your process. In production Kubernetes, you don't. With node-loop-detective v1.3.0, you can now connect to a Node.js inspector on any reachable host. One new flag: --host. That's it. loop-detective --host 10.0.0.42 --port 9229 This article walks through the practical setups for Docker, Kubernetes, and remote servers — and the security considerations you should know about. The Problem With Remote Debugging Node.js has a powerful built-in debugger based on the V8 Inspector Protocol. When you start a process with --inspect, it opens a WebSocket endpoint t