Services

Resources

Company

AI SRE

AI SRE is the use of AI agents in site reliability engineering, mostly during incident response. An AI SRE agent is a large language model (LLM) connected to tools that query logs, metrics, traces, deploy history and runbooks. It triages alerts, gathers evidence and proposes a likely root cause for an on-call engineer to verify.

How it works

An alert or incident triggers the agent. It plans a set of queries, calls tools such as a metrics API or a log search, reads the results and repeats until it can summarise what changed and where the fault likely is. The main target is mean time to isolate (MTTI), the time from page to knowing which component failed. For example, if isolation takes 40 minutes of a 60-minute incident, that is where an agent can save the most time. Its output should cite the evidence behind each claim.

Why it matters in production

An agent is only as good as the access and context it gets. With partial data it can produce a confident but wrong root cause, which slows the response. Teams should test agents on real past incidents, check their evidence, and limit them to read-only actions until they earn trust.

See also

On the One2N blog

References

  1. Effective troubleshooting (Google SRE book)

  2. Managing incidents (Google SRE book)

Comic about AI SRE: Asha is paged at 03:12 for checkout errors and the agent starts; it queries the deploy log, metrics and logs read-only; it proposes deploy a1b2 as the likely cause with cited evidence and Asha checks a citation; Asha rolls back herself, isolation took 6 minutes instead of 40, and Noor notes cited claims can be checked.