Operations | Monitoring | ITSM | DevOps | Cloud

From reactive operations to strategic value: a comprehensive guide to building an ITSM strategy that enables business agility and resilience.

At Harness, we’re committed to helping teams build and deliver software that doesn’t just work – it thrives under pressure, scales reliably, and recovers swiftly from the unexpected. Today, we’re taking the next step in that mission by evolving our Chaos Engineering module into Resilience Testing. This evolution reflects how reliability is tested in practice today.

The Netdata Cloud MCP Server is now available — giving AI agents and assistants direct access to your Netdata through a single endpoint at app.netdata.cloud/api/v1/mcp.

Whether you’re in finance or engineering, you know keeping your customers happy is the key to success. That means, your SaaS product or service needs to be available, reliable, and cost-effective virtually all the time. On that note, you can determine how stable and high-performing your service is depending on whether you use On-Demand or Spot Instances. Pricing, capacity, and flexibility will also vary depending on which of the two instances you choose.

If you have ever owned, operated, or supported a piece of technology, you have probably built a dashboard. Maybe it started as a quick chart to answer a simple question, then quietly grew into something more important. Dashboards are often created by the people who know the systems best, the ones who can wire together data sources and click all the right buttons. But those same builders are rarely trained in how humans actually interpret data.

Can you create an audit trail for what your AI agent actually did, and enforce rules about what it was allowed to do? Here’s what I found after spending a session wiring the two tools together.

2025 was the year that RISC-V readiness gave way to RISC-V adoption. It’s been quite a journey. What began years ago as early architectural exploration and enablement has matured into real silicon, systems, and deployments. In particular, RVA23 provides a stable and predictable baseline we can align on with our wider ecosystem of partners. At Canonical, we’re committed to making RISC-V a viable option for anyone who wishes to adopt it.

L1, L2, L3 is one of the most common ways to structure an escalation policy. The idea is simple: an incident triggers and lands with a first responder. If it needs more attention, it moves up the chain to someone with more expertise. This guide explains how each tier works, when this structure makes sense, and what to keep in mind when setting one up.

This is a guest post from James Hemson. For years, the test data management market has told smaller companies the same story. Test data is complex. You need consultants. Compliance is expensive. Expect a six-month implementation before you see any value. At Redgate we think that's wrong. And we think it's wrong by design. Complexity creates services revenue. It creates switching costs. Most vendors have built their businesses around this.

When a critical incident triggers, there’s no time to figure out who to call. That decision needs to be made well before the incident arrives. A dedicated escalation policy for critical incidents gives your team a clear path to follow the moment things go wrong, rather than leaving it to whoever happens to be around. This guide covers the key decisions involved in building that policy.