-
The alert channel nobody read, and the catalogue that fixed it
Every monitor paged, so none of them meant anything. Staging woke people at night, one quiet tenant could report a 100 percent error rate off a single request, and the team had learned to swipe the notification away. Here is the P1 and P2 split we settled on for an ECS stack, and the two mechanics that stopped the flapping.
-
CPU utilization lies: autoscaling a single-threaded service
A service was slow under load, but autoscaling never fired because CPU sat at 30 percent. A single-threaded app on a multi-core task saturates one core and reads as barely busy. Why, and how to fix it.