Operations | Monitoring | ITSM | DevOps | Cloud

The finance team says gross margins are slipping. Engineering says costs are under control. Then you get THE question.

The year is 2025, and I’ve been watching teams discover what happens when you give developers AI superpowers without giving them AI super-governance. It’s like the merchandising scene from Spaceballs: “Vibe Coding: The Flamethrower. The kids love this one.” But here’s the thing: I’m not here to take away the flamethrowers. I’m here to hand out fire extinguishers and maybe suggest we practice in a safe room instead of the living room.

Earlier this year, we launched relaxAI, an AI assistant designed with one paramount focus: your privacy. We’re now excited to announce the relaxAI API is in General Availability (GA) offering an OpenAI interface. This gives UK organizations up to 90% cost savings versus leading providers while ensuring data never leaves UK jurisdiction.

Cortex gives engineering teams full visibility and control over their services, from ownership and standards to service history and production readiness. Our goal is to help teams stay aligned and move faster so they are ready for whatever is ahead. The reality for any engineering team is that developers spend the most of their time in their IDE, not their IDP. And while developers love the context Cortex provides, they don’t love context switching.

We’re constantly improving DataStream to make security data management simpler, smarter, and more efficient for modern SOCs. This latest update introduces new capabilities that bring even more visibility and flexibility to your telemetry pipelines. Let’s take a closer look at what’s new.

As distributed systems scale, maintaining manual instrumentation across services quickly becomes unsustainable. The OTel Injector addresses this by automatically attaching OpenTelemetry instrumentation to applications, no code changes needed. This blog covers how the OTel Injector works, how it integrates with Linux environments, and how to set it up for consistent telemetry across your stack.

How we cut CI cycle times and flaky builds in half, and maintenance downtime to zero.

Grafana Loki is up and running, log ingestion looks healthy, and dashboards are rendering without issues. But when you query logs from a few weeks ago, the data's missing. This is a recurring problem for many teams using Loki in production: while the system handles short-term log visibility well, it often lacks the retention guarantees developers expect for historical analysis and incident review.