Operations | Monitoring | ITSM | DevOps | Cloud

When everything on the internet comes with an “AI-powered” tag attached and AI fatigue is in full gear, we come to the rescue with a list of tools and services for DevOps and SREs. No AI included. Twelve tools across infrastructure, security, observability, and incident management. Mostly open source. All of them solving specific problems without a chatbot in sight.

Your monitoring fires at 2 AM. The on-call engineer picks up but doesn't know who to call next, what information to include, or which Slack channel to use. Sound familiar? That's what happens when escalation procedures exist only in people's heads — or worse, don't exist at all. The fix isn't complicated: a documented escalation procedure that every team member can follow under pressure. The problem is building one from scratch takes hours.

This is a comprehensive reference of every HTTP status code defined in the HTTP specification (RFC 9110) and common extensions. Use it as a quick lookup when you encounter a status code in your browser, server logs, or API responses. For a beginner-friendly guide to the most common codes, see From 200 to 503: Understanding the Most Common HTTP Status Codes.

Note: This blog post is co-authored by Daniel Shechter, CEO and co-founder of Miggo Security. Modern runtime security is critical to understand complex systems and detect and protect against attacks, especially in rapidly evolving cloud native architectures. For many security teams, however, achieving deep visibility into runtime risks remains a moving target.

This is a guest post from Phil James. Database teams are already juggling a lot. Monitoring the performance of complex, multi-platform estates takes expertise and focus — and that's before you factor in installing, maintaining, and updating the monitoring tooling itself. That's the tension we've been hearing from database teams for a while. The monitoring solution is supposed to reduce operational burden, yet the infrastructure that runs it adds more.

This is a guest post from udara.ratnakumara. In a recent webinar I hosted with my colleague Chris Hawkins, Inside a DBA’s Day: What Really Happens and How to Stay Ahead, we talked through the realities of a typical DBA day and the practical ways teams can stay ahead of issues rather than constantly reacting. For many DBAs, the day doesn’t start with coffee. It starts with an alert. A report is suddenly slow. An application query is timing out.

The world is generating data at a pace that defies the human ability to draw insights and comprehend. By 2028, we’ll reach almost 400 zettabytes of global data—with over 55% of it coming from machines talking to machines. For enterprises, this isn’t just a storage problem; it’s an existential challenge.

--- ‍Key Takeaways --- AI can generate code in seconds. It still can’t ship software safely. That gap isn’t about model quality or prompt engineering. It’s about context, and most software organizations don’t have a system that accurately reflects how pipelines, services, environments, policies, and teams actually relate to each other. Without that context, AI doesn’t automate delivery. It amplifies risk.

AI is changing both what you build and how you build it - at the same time. Today, Harness is announcing two new products to secure both: AI Security, a new product to discover, test, and protect AI running in your applications, and Secure AI Coding, a new capability of Harness SAST that secures the code your AI tools are writing.

We hear a lot of war stories from the teams we work with. Horror stories about cloud bills, surprise overages, and the infrastructure decisions that seemed perfectly reasonable at the time. This one comes from Erik Dasque, CTO at Allure Security. It involves a junior developer, a Kubernetes CronJob, and a recurring bill that, if not caught, would have happened on a yearly basis.