I spent the better part of a day convinced that Azure Monitor SLI alerting could not be deployed as infrastructure as code. I wrote a parallel implementation to work around it.
I was wrong, and th...
Want to keep yourself up to date with the latest news from Luke.geek.nz Blog?
Subscribe using the "Follow" button below and we provide you with customized updates, via topic or tag, that get delivered to your email address, your smartphone or on your dedicated news page on follow.it.
You can unsubscribe at any time painlessly.
Title of Luke.geek.nz Blog: "Bluesky"
Is this your feed? Claim it!
I spent the better part of a day convinced that Azure Monitor SLI alerting could not be deployed as infrastructure as code. I wrote a parallel implementation to work around it.
I was wrong, and th...
Azure Monitor now does SLIs and SLOs natively, with error budgets and burn rate alerting, which is good news if you have been hand-rolling multi-window burn rate rules out of metric alerts for years. I have been building a demo that pairs Azure Monitor SLIs with the Azure SRE Agent on AKS, all deployed with the Azure Developer CLI, and I wanted every part of it in infrastruct...
Most Kubernetes monitoring tells you that a pod restarted. It rarely tells you whether a customer noticed, which customers were affected, or whether the business promise is now at risk.
That gap is a product and service-design problem as much as a monitoring problem. The people responsible for a payment journey need to know whether checkout works, how quickly it works,...
Every codebase that has lasted long enough builds up at least one layer like this. Request stubs call into a wiring dict: a lookup table of small lambda functions, one per route, that exists only to find the right handler. Those lambdas call translation functions that move data between an old dispatch shape and what the framework now wants on its own. It worked when it was wr...
Execution-Ledger is an open-source durable workflow orchestrator I built in Rust on Azure Container Apps. It handles step-level idempotency, targeted replay, and compensation for long-running jobs that span external systems. This post is about why I chose Rust, why I cho...