Operations | Monitoring | ITSM | DevOps | Cloud

When an incident triggers, the question is not just what broke but also how urgent it is and who on your team needs to respond. Alert Routing rules answer those questions automatically. You define the conditions once and the right response follows every time an incident triggers. Every Alert Routing rule does one or more of these three things: Three conditions drive all of it: incident payload, time of occurrence, and frequency.

Most teams know they are spending money on AI in production. Far fewer realize how much they are spending outside production. It’s easy to get lost as you evaluate which model has the best responses, is fast enough, and cheap enough to run in production. That is because the AI bill usually shows up as a giant blob. It is easy to see the total.

Early in his career, Kelsey Hightower made a bet. The load balancer his team was running was consuming too much memory, and he was convinced he knew the fix. He told his manager: “If it doesn’t work, fire me. But I think I can make it work.” The fix was HAProxy. It was a story he shared publicly for the first time at HAProxyConf 2025, where he delivered a keynote address, “The Fundamentals.”

During International Women’s Month, we celebrate women whose technical work changed entire industries. But the lessons from engineers like Margaret Hamilton aren’t seasonal, they’re fundamental to how we should approach software development every single day. Margaret coined the term “software engineering” and built the code that landed humans on the moon. Her approach to rigor is as relevant to your next Git commit as it was to Apollo 11’s descent engine.

Most engineering teams don’t migrate their on-call and paging systems unless absolutely necessary. No matter how painful their current solution, it's one of those changes that people put off for as long as possible because the cost is real. The disruption, the retraining, the risk of missing a critical page during the transition. It's not something you do on a whim.

Today, we’re excited to introduce the beta release of MicroCloud Cluster Manager, a new way to discover, organize, and operate your MicroCloud environments from a single, unified interface. MicroCloud is an open source cloud platform that makes it simple to create lightweight, resilient clusters anywhere. As teams scale from one cluster to many, visibility and coordination quickly become essential. Cluster Manager is built to solve exactly that.

How platform and SRE teams are using Mezmo's open-core agent framework — with any LLM, any tools, any observability backend.