Operations | Monitoring | ITSM | DevOps | Cloud

Overview of AI Evaluation (The Context Window #05)

Can you actually trust an AI agent? In this pre-recorded episode of The Context Window, Nicole van der Hoeven sits down with Yas Ekinci, an engineer on the Grafana AI team, to talk about evals — how Grafana measures the quality and reliability of the AI it ships. They get into the difference between online and offline evals, why reviewing AI-generated code has become the real bottleneck, the "final answer problem" of plausible-but-wrong outputs, and o11y-bench, Grafana's open benchmark for observability agents. Along the way.

How AI-First Operations Unlocks Compounding Engineering Productivity

Engineering teams have plenty of ideas, but they’re often short on time to act on them. As software systems grow more complex, an increasing share of engineering capacity is consumed by non-building activities: investigating alerts, coordinating fixes, and managing operational incidents. Every hour spent diagnosing failures is an hour not spent shipping features or experimenting with new product ideas. Over time, that lost capacity compounds.

Creating an agentic feedback loop with reliability guardrails

Reliability guardrails help make sure that your applications stay reliable without slowing down. In an earlier blog, we went into why agentic AI development needs reliability guardrails. It went over how the increased speed of AI development demands automated guardrails to verify resilience and what kinds of tests these guardrails should cover. But that’s only the beginning. By themselves, guardrails act as a gate to ensure resilience mechanisms hold under rapid changes.

How AI Scribe Medical Tools Improve Healthcare Efficiency

Healthcare workers spend a huge part of their day on paperwork instead of patients. Doctors often joke that they trained for years to practice medicine, only to spend half their time typing notes into a computer. This is exactly the problem that AI scribe medical tools are designed to solve.

Achieving sovereign and secure AIOps with Ollama and OpManager

Enterprise IT networks power business operations across the world. As businesses scale to catch up with an increasingly-demanding user base, networks also grow more complex. IT teams managing these networks have to monitor more data than before, under more stringent SLA terms, with little room for failure. Trying to do this manually across thousands of devices can take a lot of time and effort, and are prone to errors.

New in Kubex: KAI Scheduler Integration for Shared GPU Inference

Today, we’re launching Kubex support for the KAI Scheduler and automated GPU sharing for inference workloads. As AI inference moves into production, platform teams are being asked to serve more models, support more teams, and control GPU costs at the same time. But many inference workloads do not need an entire GPU all the time. When teams reserve full GPUs or oversized GPU fractions to stay safe, expensive capacity can sit idle across the cluster.

Multi-Agent Architectures - What we shipped, what broke, and what we'd do differently

At LLMday Lisbon, our Software Engineer, Viktor Vasylkovskyi, highlights the realities of building production AI agents with LangGraph - sometimes getting it right, often learning the hard way. This talk is about what was actually shipped, including a distributed multi-agent setup at PagerDuty. Viktor breaks down the real tradeoffs between LLM-driven and deterministic orchestration, what broke, and how he’d approach it differently now.

Why you should use Language Server Protocol (LSP) with Claude Code

Agentic coding tools like Claude Code can write, refactor, and debug across an entire codebase, but by default they read code as plain text, the way grep does. The Language Server Protocol (LSP) changes that: it’s the same code-intelligence layer an IDE uses, and wiring it into an agent lets it read code by meaning instead of by string match. The bigger the codebase, the more a wrong guess about a symbol costs, and the more that structural view pays off.