debugging-techniques

Use kubectl debug to add an ephemeral container with debugging tools, since distroless images have no shell. Run kubectl debug -it <pod> --image=busybox --target=app --share-processes to inspect the app's processes, network, and files.

Delve is the official Go debugger with first-class goroutine support. Use dlv debug to start a session, then goroutines -t to view all goroutine stack traces and identify deadlocks or blocked channel operations.

Use debugpy, which is included in the VS Code Python extension. Configure a launch.json entry with type python and request launch, or use debugpy.listen() with remote attach for code running on servers or in Docker containers.

No, interactive breakpoints block execution and impact all users. Instead use structured logging with correlation IDs, distributed tracing via OpenTelemetry, and error tracking platforms like Sentry to investigate production issues safely.

The variable may have been moved due to ownership rules, or optimized out in release builds. Always debug with cargo build (debug profile) and temporarily use clone() if you need to inspect a moved value.

Propagate a correlation ID through X-Correlation-ID headers and include it in every structured log entry. Combine this with OpenTelemetry distributed tracing to view the full request timeline in tools like Jaeger.