Menu

1 / 4

The Simulator, Not the Archive: Your AI SRE Learns Somewhere Else

DEV Community: kubernetes·Nati Shalom·1 day ago
#5MeRDIHy
#devtokubernetes#devto#dev#agent#fault
Reading 0:00
15s threshold

Originally published on data-agent.co .

Machine learning changes incident remediation only when the agent learns from verified outcomes, not from history. An incident archive records one unrepeatable response per failure, so training on it clones what tired humans did. An autonomous SRE should learn the other way: by replaying engineered faults in a sandbox and grading every fix against a known answer.

The simulator, not the archive: the follow-up to the harness argument. An agent that acts on production learns the way pilots learn: by replaying failure in a controlled environment, against an answer key. History only tells you what to rehearse.

In June, a post-KubeCon autopsy on r/sre cut through the noise with a single, organizing insight: features are noise; trust is the signal. The consensus from the engineers on that thread was blunt and uniform. Investigation is fine. A drafted remediation is acceptable. A pull request is perhaps tolerable.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.