Operations | Monitoring | ITSM | DevOps | Cloud

We use Sentry's new Regex search for Logs to hunt for non-obvious bugs in our app. What do you do when traces show that Postgres jobs are backing up? Logs are trace-connected, so by looking at one of the affected traces, we can see all of the logs on that trace. In there, we can see Postgres has logged that it acquired a lock only after a long wait. Using regex, we can find all of these logs that describe acquiring a lock after a 10-second-plus wait. That narrows our search from thousands or hundreds of logs down to about a dozen.

Join Serge for an introduction to tracing and how it applies to AI agents. Through live walkthroughs, you’ll see how to follow an agent’s execution, inspect model and tool calls, and find where things went wrong. No prior tracing experience is needed.

We turned the mic around for this episode, with Zoe Hawkins interviewing Adam White and Jake Lee about Sumo Logic’s redesigned free trial. The new 14-day sandbox comes preloaded with realistic data feeds, Cloud SIEM, and our AI agents, so no one has to build collectors or open tickets before finding out whether the platform fits. Adam and Jake walk through the guided “choose your own adventure” paths, the broad, open-ended questions that bring out the best in Mobot, and how the trial will keep pace with new releases.

Why did we do this? Not important: jump to 1:31 to see the Pis. TL;DR: We stuck Minecraft on kubernetes running on 4 Raspberry Pis in a 3D-Printed case, and monitored it with open source observability. Huge thanks to Percona DBA Ivan Zaitsev for putting the demo together for Percona University, Montevideo. Coroot automatically collects and visualizes all your telemetry data: logs, metrics, traces, profiles, and a complete map of your services. With the complete context of eBPF, it can diagnose the exact cause of an incident in seconds, and show you the exact commands to fix it.

DORA's data shows that as AI adoption goes up, individual effectiveness rises, and so does software delivery instability: more rollbacks and more unplanned rework. Nathen Harvey of Google's DORA team explains why AI acts as an amplifier of whatever system you already have. He walks through the seven capabilities that separate teams getting real gains from teams drowning in downstream chaos. He also argues that the risks stopping you from shipping AI-built work should become your platform roadmap.

AI can write 1,100 lines of code for a loading spinner in five minutes. Your change board still meets once a week. Karthik Jayaraman, VP of Information Technology at Fiserv, explains what happens when code generation speeds up and everything downstream stays the same. He covers why "human in the loop" doesn't scale, why handing all review to AI backfires, and why an agent told not to touch production needs a boundary it can't cross, not just an instruction.

Turns out telling coding agents what to do over and over again doesn't actually make them better at fixing CI failures.