Operations | Monitoring | ITSM | DevOps | Cloud

3 a.m., the pager fires, and the runbook describes a service that shipped three versions ago. Ask the agent what the cluster actually has instead. Runbooks go stale because clusters change faster than documentation does. Every deploy, every new service, every renamed alert widens the gap between what is running and what is written down.

On this episode of Masters of Data, we dig into what happens when AI actually delivers on its promise to eliminate busywork, and explore why removing the toil doesn't feel like the win everyone expected. We make the case that repetitive tasks build the intuition, pattern recognition, and muscle memory people need to do the harder work well. Security and engineering leaders rethinking how much triage and busywork to hand off to AI will find plenty to chew on here, especially anyone staring down a task list where every single item feels like the hardest one.

Your competitive edge isn't the model; it's the data that only you have. Sonal Pardeshi, Head of AI Product at Splunk, explains why teams building on general-purpose models keep arriving at the same generic outcomes, and what changes when agents are grounded in your own machine data and your own governance. AI Toolkit and Agent Launchpad let teams build and run agents against your grounded data.

1,133 requests failed on one bad commit. The patch and the regression test are already written by the time anyone is asked to read the exact diff. This demo runs AURA as one step inside a Temporal workflow, alongside Codex. A GET request against a product catalog service goes from success to HTTP 500, and ClickHouse records the version, commit, trace ID, and exact error for every request. By the time AURA investigates, all 1,133 requests on that version have failed.

#claudecode #optimization #aicoding #observability

Checkout starts failing because the cart service keeps dying. The real cause is a recent pull request that let memory grow with every add to cart.

The same agent that reads a Kubernetes cluster reads a Windows machine. One MCP server, one config entry, and the questions are the ones you already ask.

You get an answer from the agent and no way to check how it got there. The route it took is recorded, and so is the reason it gave for taking it. AURA emits OpenTelemetry spans, and the Docker quickstart wires them straight into Phoenix. Four services come up together: AURA Web Server as the persistent agent harness, LibreChat as a browser interface for chatting with the agent, Phoenix to receive the spans, and MongoDB to store stateful data for LibreChat. The Compose file arrives pre-configured to point AURA at Phoenix and to enable content recording for the local demo.