Operations | Monitoring | ITSM | DevOps | Cloud

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

Language AI to physical AI explained

What is physical AI? Physical AI embeds machine learning directly into hardware, enabling algorithms to interact, move, and perform autonomous tasks in the physical world. Traditionally, robots relied on precise, hardcoded coordinates; if an object shifted by a single millimeter, the entire system failed. Today, robotics is moving past rigid automation toward truly adaptive architecture. Neural networks help machines process raw sensor data in real time. Consequently, machines can dynamically reason through the unpredictable physical world.

High Cardinality in ClickHouse at Scale: What Actually Breaks

ClickHouse swallows high-cardinality telemetry at ingest, then breaks at query time weeks later. Here is what fails, and how we keep it fast in production. Prathamesh works as an evangelist at Last9, runs SRE stories - where SRE and DevOps folks share their stories, and maintains o11y.wiki - a glossary of all terms related to observability.

The debugging crisis nobody's talking about: AI, abstraction, and the skills gap

Here's a scenario that's playing out in engineering teams across the industry right now. A developer uses AI to rapidly prototype a microservice. The code works. They deploy it to production. Six months later, something breaks. The system is under load, a database connection pools, and the service starts failing in subtle ways. The engineer pulls up the code, but here's the problem, they didn't write it. An AI assistant did. They don't understand the flow deeply. They don't know where to look first.

Cortex catalog data now flows into Rootly

Incident response is a context problem. The first minutes of any incident are spent reconstructing what the affected service is, what it depends on, and who owns it. That reconstruction happens during the worst possible window. The Cortex catalog already holds this data: services, teams, domains, and the relationships between them, maintained by the engineers who run those systems.

How Kubernetes Operators May Conflict With Resource Optimization (And How to Avoid It)

A Kubernetes Operator is a method of packaging, deploying, and managing a Kubernetes application. It extends the native Kubernetes API by combining custom resources (CRDs) with a dedicated controller: a custom control loop that continuously watches the state of those resources. The primary purpose of an operator is to automate complex, stateful applications (like databases, message queues, or monitoring suites) that require human operational knowledge to maintain.

How AI is changing platform engineering

AI is changing software development fast. But what does that actually mean for platform engineering teams? In this conversation, Civo's John Dietz and M R Rishi dig into what they're seeing on the ground, the 10x effect of AI on app count, what it means for platform team workloads, the debugging skills that are quietly being lost, and whether Kubernetes itself might eventually become just another abstraction.

Agentic Pipelines now supports OpenAI Codex

Bring your Codex agent into Bitbucket Pipelines. A few weeks ago, we announced support for Claude agents in Bitbucket Pipelines. Today, we’re adding OpenAI Codex as a supported agent. If your team is already using Codex on the desktop, you can now move that same workflow into your pipeline — triggered by a merge, a schedule, a failing build, or a pull request comment.