Microsoft Tech155 viewsI kept refreshing the Azure portal, waiting for an alert. That's when it hit me: my alerts were working perfectly. They just weren't designed for this failure mode.
The problem every developer knows If you're a developer or DevOps engineer, you've been here: a customer reports an issue, you scramble to check your monitoring, and then you realize you don't have the right alerts set up. By the time you find out, it's already too late. You set up what seems like reasonable alerting and assume you're covered.
They slip through the cracks of your carefully planned thresholds. MY SETUP: Aks with redis I love to vibe code apps using GitHub Copilot Agent mode with Claude Opus 4.5. It's fast, it understands context, and it lets me focus on building rather than boilerplate.
For this project, I built a simple journal entry app: * AKS cluster hosting the web API * Azure Cache for Redis storing journal data * Azure Monitor alerts for CPU, memory, pod restarts, container errors, OOMKilled, and job failures Seemed solid. THE SCENARIO: Redis password rotation Here's something that happens constantly in enterprise environments: the security team rotates passwords. And it breaks things when apps don't pick up the new credentials..
Official source
Microsoft Tech