Operations | Monitoring | ITSM | DevOps | Cloud

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.

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.

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.

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.

At incident.io we run a deliberately simple technology stack. Keeping things boring has allowed us to scale from a few hundred customers to several thousand, while having only two platform engineers. In this post I'll walk through the stack, explain some of the choices we've made, and touch on the challenges we're facing as we grow.

Bare-metal. Just reading that word might trigger a physical reaction for some of us. Dusty closets, old server rooms, and loud rigs that never seemed to work quite right. Remember waiting days for IT to provision a server, only to realize your ticket got lost in the shuffle? Or the classic "well, it worked on my machine" excuse right before a production push? Ah, the good old days.

An escalation policy is the route an incident takes after it triggers. It lays out who gets alerted first and sets a wait time. If nobody responds, it moves the incident forward to the next person. The word “escalation” is worth pausing on. When an incident triggers and the first person doesn’t respond, the incident doesn’t sit and wait. It moves to the next person and keeps moving until someone picks it up. That forward movement is the escalation.