Skip to content

Comment on Full technical details on Asana's worst outageparent

Comments

What I don't get is why you didn't see the relatively low cpu usage on the database server and the super high ones on the webserver immediately in a nagios (or similar) dashboard.

They were distracted by the previous experience of having issues elsewhere.

And apparently there were no alarms in place for these kind of things

Apparently a lot of parts of the system were on alarm.

It's because they don't have a simple rollup dashboard that you can see that at a glance, like most places. Can you imagine if your car just showed you an event log for a door open, oil, turn singles on etc. that's what most monitoring systems are like these days.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.