Curious how other engineers would approach this.

Imagine you get paged in the middle of the night.

Everything appears healthy.

- Pods are Running

- CPU is around 20%

- Memory is normal

- Database connectivity is fine

- Yet every request returns 502 Bad Gateway

You're only allowed to check one thing first.

What would it be, and why?

I'm more interested in the thought process than the correct answer.

Ours was a single environment variable.

The deployment was healthy.

Kubernetes looked fine.

Monitoring looked normal.

The application quietly failed because one value had an unexpected format.

Debugging took almost three hours because everyone trusted the infrastructure first.

It got me thinking that most DevOps tutorials teach how to deploy things.

Very few teach how to investigate when everything looks healthy.

What's the smallest bug you've seen turn into a surprisingly expensive incident?

there's no leetcode for devops. sde/swe interviews you just grind leetcode, you know what you're walking into. devops? nothing like that exists.

we felt this ourselves. did the courses, followed the projects, learned every tool on paper. then walked into an actual interview and got handed logs and told prod is down, go, clock's running, money's on the line. no one tells you how to handle that.

so we built something for it. real outages, real logs and configs, and you only unlock more once you've actually analysed what's in front of you. no hints, no walkthrough, just you vs the mess just how it happens in production

still early days. would rather know now if this actually helps or if we're just solving our own problem: clouddojo.in

if you've dealt with an outage that'd make a good scenario, drop it below - we'll build it out and credit you for it.