When searching for bugs in our Go applications I used to use many tools like testing, profiling, logging, and so on.

One tool I didn't use back then was the Go debugger (Delve) because, despite being very effective, it seemed intimidating and difficult to start and use. Moreover, today more and more Go applications are deployed and running in a Kubernetes cluster which makes the task to run the debugger even more intimidating and difficult.

Today, the Delve debugger is my main tool for searching bugs in my Go applications, wherever they are located, and with this talk I wish to share with everyone how to start a debugging session with Delve, going gradually from starting Delve for a Go application in my local development environment, then for the same application running inside a Docker container and eventually still for the same application deployed in a Kubernetes cluster.

My objective with this talk is to give an introduction on how to start Delve to debug a Go application and, with this knowledge, make debugging a less difficult and intimidating tool to find bugs.