Operations | Monitoring | ITSM | DevOps | Cloud

Last year was the year of AI code generation. This year is everything that comes after: validation, quality, and making sure what gets built actually ships. Nobody's better positioned to talk about that than CircleCI, and in this episode of Peer Review, CFO Blake Buisson and CMO Chitra Balasubramanian dig into what that moment means for the company and the people building it.

Steve Flanders (Senior Director of Engineering, Splunk) makes the case that AI can't save an observability stack that never agreed on a standard. Mix formats across metrics and logs, and AI stops correlating and starts guessing, which means you either make the wrong call or miss the answer you actually needed. OpenTelemetry is one fix, but Prometheus and Fluentd work too. The standard matters more than which one you pick.

Learn more at speedscale.com.

We look at these pictures together, okay? One time.

NinjaOne Field CTO Jeff Hunter demonstrates how to set up a PXE server, or Preboot Execution Environment server, by configuring Windows Deployment Services on a Windows server. This gives teams a way to boot into WinPE without requiring a USB drive, and works more efficiently at scale. Chapters.

One integration token, one config file, no code. AURA routes the question to a runbook-reader worker, queries Notion, and answers from what your team wrote.

A root cause is not a fix. AURA keeps working the problem, taking what you find on the host and coming back with the user ID mismatch behind the failure. What follows a root cause is normally manual: check the mount, compare ownership on the host against the user inside the container, and get it wrong at least once before it lands.

There's a risk window after a malicious package is published when nobody knows it's there. Scanners alone can't close that window.

A coworker says checkout is broken and nothing else. That is the whole prompt. AURA reads the live logs and comes back with the payment service. Normally a message like this is the start of guessing at a service and opening dashboards until something looks wrong. Here it is the entire input: no service named, no error string, no time range.

How well do the Redgate Advocates know SQL Server? Find out in this quick-fire quiz, recorded live with an audience at SQL Saturday Day of Data Baton Rouge on July 18th!