AI Agents Prove System Reliability Before Outages Hit
8m 5s
System reliability has always depended on finding weaknesses before customers do. AI is now changing how that work gets done. Teams can test, fix and verify faster than ever.
Gremlin Co-founder and CEO Kolton Andrus examines that shift with Alan Shimel at KubeCon + CloudNativeCon in Salt Lake City.
From Expert Tool to Everyday Practice
Andrus worked as an engineer at Amazon and Netflix, keeping large systems running. Those teams pioneered chaos engineering. Gremlin was founded to bring those lessons to everyone.
The first product was an expert-level SRE tool. It delivered value, but users needed deep knowledge. Over 10 years, Gremlin added test suites and reliability scores to make good practice easier.
Find, Fix and Prove
Gremlin's new Foresight AI takes the next step. It analyzes a system, explains what could go wrong and recommends tests. Then it runs them.
It reviews the results, works out what failed and proposes a fix as a diff or pull request. Andrus says the most important part comes next. Foresight runs the test again to prove the fix worked.
That step separates a real fix from a patch on a symptom. Teams end up with evidence, not assumptions. They know the system can handle that failure.
Built for Kubernetes
Many Gremlin customers now run on Kubernetes. Because Gremlin installs as a container, Foresight can query the cluster in real time. It can suggest changes to Helm charts or Flux configurations.
Andrus sees Kubernetes as an accelerator for AI applications. Teams benefit from years of shared learning instead of reinventing the wheel.
Local or Frontier Models
Alan notes the pendulum swinging back toward on-premises AI. Andrus agrees that data sovereignty matters to many customers.
Foresight can use a frontier model through an API or run against a local model. Customers can point it at their own model and still use Gremlin's failure analysis. Meeting customers where they are is key to system reliability at scale.