Operations | Monitoring | ITSM | DevOps | Cloud

The latest News and Information on DevOps, CI/CD, Automation and related technologies.

Escalation policies for critical incidents

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.

Feature Friday: New Bird's Eye Report

Stop squinting at data and start driving engineering excellence. In this week’s Feature Friday, Christine from the Cortex Product Team introduces the all-new Birdseye Report (now in private beta). See how to master your engineering standards at scale. We’ve redesigned Birdseye to give you a true "top-down" view of scorecard performance across your entire organization—from the CTO level down to a single service.

The Complexity Myth in Test Data Management

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.

Understanding L1, L2, L3 escalation policy

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.

Canonical and Ubuntu RISC-V: a 2025 retro and looking forward to 2026

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.

Managing AI Models and Datasets with Harness Artifact Registry | AI/ML Artifact Management

Building AI applications often means juggling multiple models, scattered datasets, and version chaos across local systems. But what if you could bring it all together — securely and efficiently — in one place? In this walkthrough, Shibam Dhar, DevRel Engineer at Harness, demonstrates how Harness Artifact Registry makes it easy to manage and govern your AI/ML assets — from models and datasets to prompts and agents — with built-in support like Hugging Face and generic registry types.

Unmasking the Resolute Raccoon

You’ve almost certainly seen them… In the forest, rummaging through a dumpster, in poorly aging millennial memes. Raccoons are ubiquitous and endlessly entertaining creatures. YouTube and TikTok are full of videos documenting their clever antics and escapades. One such intrepid raccoon gained fame for making their way to the most unlikely places, from liquor stores to karate studios.