Operations | Monitoring | ITSM | DevOps | Cloud

Your AI agent can read every log, metric and trace in seconds. It still can't tell you why things broke. At Civo Navigate London, James Herbert of groundcover explains why AI SRE agents need that context to travel the whole development lifecycle. He shows how agents embedded in the tools where software is built and run can move from isolated tasks to investigating and acting with the full picture.

What if AI could find a security vulnerability, determine whether it actually matters, write the fix, validate it, and open a pull request for review? In this demo, see how Harness Security Testing Agents work together to move from vulnerability detection to a verified fix with an audit trail along the way. The system uses three agents: Harness can analyze where vulnerabilities exist in your environment, determine whether they’re actually reachable, prioritize what needs to be fixed, and automatically create remediation pull requests.

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.