SSHing into a container for troubleshooting or burdening it with additional monitoring tools is kind of an anti-pattern. But… you still want to have full control, traceability and visibility right? Containers are highly volatile, how can you do this if your container doesn’t exist anymore?
Sysdig uses Linux tracepoints to collect and then process and filter kernel system calls and events. Still this requires a deep knowledge on a tcpdump like filtering syntax and understanding on the syscalls involved. Sysdig Inspect makes our deep dive into system calls much more intuitive and visual though a graphical user interface that allows to correlate high level activities like containers, processes, containers, network or file I/O and commands, events or logs.
In this webinar series you will get to know how Sysdig and Sysdig inspect works through a series of practical examples:
-Exploration and performance analysis of container, processes, network and file activity on a typical Wordpress setup
-Debug a 502 HTTP error on a load-balanced Python app with HAproxy
-Troubleshoot a Kubernetes CrashLoopBackOff error
Who should attend?
If you're managing containers in production, using containers for development or just beginning our container exploration, you'll want to attend to understand the challenges of troubleshooting system or application errors when running inside containers.