Frigga Blogs

A node memory alert goes off. The question that follows is always the same, and it's never as easy to answer as it should be. Which workload is doing this? The usual route is kubectl top pods , sorted by hand, one namespace at a time. If you…

Every investigation I have been part of needs two kinds of knowledge, and they never live in the same place. The first is what production is doing. Error rate, latency, memory, what deployed and when, which pods are unhappy. That is Grafana, or Data…

Watch how an investigation actually begins. An alert fires. Somebody in the channel says "I bet it's the database." Within ninety seconds four people are looking at database metrics, somebody is checking connection pool saturation, and a…

Nearly nine in ten organisations now run more than one cloud. Flexera's 2026 State of the Cloud report puts multi-cloud adoption at 89%, and the average sits at around 2.6 providers. Almost none of them chose this. Multi-cloud is usually th…

There is a question that stalls almost every incident I have been part of, and it arrives about four minutes in. Something is failing. You have found the service responsible. Then somebody asks what else touches it, and the room goes quiet. Two peop…

Open your Grafana instance and look at the list. Not the two or three you actually use. The whole list. Most of those panels have an origin story, and it is nearly always the same one. Something broke, nobody could see it while it was happening, and…

Picture a database going down for ninety seconds. Nothing dramatic, a failover, the kind of thing that should be invisible. Every pod in your deployment runs a liveness probe that opens a connection to that database and runs a trivial query. Every o…