Operations | Monitoring | ITSM | DevOps | Cloud

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

Designing exceptions that developers won't route around

Every dependency security program needs a way to handle packages that have a valid business reason to stay in use despite a CVE or license issue. Ideal exception processes give developers full context upfront, including safer alternatives, then route real requests to a security team that weighs the risk profile and logs who requested it, who approved it, and for how long. Get the friction wrong in either direction and the process fails: too much and developers route around it, too little and it becomes the default path.

Claude Code + Harness | Software Delivery for the Agent Era

Claude Code changes how fast software gets written. Harness changes whether you can trust what shipped. In this video, watch how autonomous AI agents handle end-to-end bug fixing, security remediation, and deployment verification—all within an automated Harness pipeline. From reading a ticket to running canary deployments and self-healing broken manifests, see how engineering teams can deliver software faster without sacrificing quality or security.

Best IT Orchestration Tools for ITSM: 5 Platforms Compared

What are the best IT orchestration tools for ITSM? Compare Resolve, ServiceNow, PagerDuty, BigPanda, and Splunk ITSI across workflow automation, governance, integrations, alert correlation, incident response, and enterprise scalability. In this video, you’ll learn: These platforms are not identical. Resolve focuses on orchestrating workflows across systems. ServiceNow centers automation around ticketing and CMDB governance. PagerDuty specializes in incident response. BigPanda focuses on event correlation and triage, while Splunk ITSI provides service intelligence and event analytics.

Kubernetes GPU Scheduling for MLOps and GPU Sharing

The default Kubernetes scheduler was built for stateless services: web servers, APIs, databases. It schedules a pod, checks that a node has enough of whatever resources were requested, and binds it. For CPU and memory, that model works fine. For GPUs, it falls apart in three specific ways. First, GPUs are treated as an opaque integer resource.

Redgate Monitor's Product Updates - August 2026

This month, we wanted to spotlight some of the new cloud features that shipped last month and are enabling teams to keep pace with database estates that increasingly span multiple platforms and providers. We also have updates for Monitor Enterprise users that improve alerting for permission changes. Here's what's new in Monitor.

Are AI Coding Agents the New CI Bottleneck?

AI coding agents are moving the software bottleneck from writing code to validating it. Here’s what that means for CI infrastructure, capacity planning, and software quality. This topic is explored in more detail in “CI Can’t Keep Up With AI,” an episode of Uplink, where Aditya “JP” Jayaprakash, Co-founder and CEO of Blacksmith, discusses how AI coding agents are reshaping CI and software delivery. Table of Contents.

A practical guide to risk-based code review

Traditional code review no longer keeps pace with how much code teams are shipping. Risk-based code review is the response: instead of giving every pull request the same scrutiny, you route human attention by risk, letting low-risk changes ship with light or automated review and reserving deep human review for the changes that are expensive to get wrong.

What your AI SRE can't see (and what you can do about it)

AI SRE is having a moment. The category pulled in massive funding rounds over the last two years, Gartner published its first market guide, and vendors are promising everything from 90% faster resolution to fully autonomous incident response. If you run an engineering organization, someone has probably pitched you an AI SRE in the last quarter. And let’s be honest: faster triage, less alert fatigue, and automated frontline response are wins for understaffed teams.

When Your SQL Table Outgrows Itself: Lessons from Refactoring at Scale | Harness Blog

At Harness, we build an AI-powered software delivery platform, and test result data is core to how we help engineering teams ship faster. The table that stores it started small: one row per record, all the context right there on the row. Simple, readable, and it worked. Until it didn't. This is the story of how we refactored it, what we learned, and what I'd tell you to watch for in your own systems.