Debugging GitHub Actions

Namespace gives you direct access to your running workflows and deep visibility into their performance. Reach for interactive access when you need to get inside a job as it runs, remote display when you need a graphical session, performance metrics and logging when you are analyzing a run after the fact, OOM detection and crash dumps when a job fails unexpectedly, and queue time when jobs are waiting to start.

Interactive access

Interactive access
Pause a running job, set breakpoints, and SSH into the runner instance.

Remote display

Remote display
VNC into macOS runners and RDP into Windows runners.

Performance metrics

Performance metrics
Correlate job steps with CPU, memory, disk, and network metrics and compare against previous runs.

Advanced logging

Advanced logging
Container logs, build logs, and step-to-metric correlation beyond standard GitHub Actions logs.

OOM detection

OOM detection
Make out-of-memory conditions explicit instead of guessing from allocation graphs.

Crash dumps

Crash dumps
Automatically collect crash dumps and store them as artifacts for forensic analysis.

Queue time

Queue time
Investigate queue time with the insights view and concurrency usage.

Hands-on support

Got stuck? Need help with debugging one of your workflows? Our team is here to assist:

• Technical Support: Reach out to support@namespace.so to talk to one of our engineers.
• Community: Join our community Discord to learn about tips and best practices.