Quickly Turn ALB/ELB Status Codes into an Issue-Seeking Heatmap
More often than not, as developers, when we get a report that a large customer is hitting 502 errors, there's a flurry of activity. What's wrong? Is something deeply broken? So you start digging through AWS logs to see what you can find, but it's hard to reproduce. Sometimes, there's no clear answer, and you move on without any resolution. What if I told you it doesn't have to be this way?