Radar - You don't need an AI SRE. Give your agent Radar.
by•
Your agent knows Kubernetes. It doesn't know your cluster. Radar (open-source) gives it context over MCP: ranked issues, a change timeline, logs and owners in one view. New: click Investigate on a failing workload. Claude Code, Codex or Cursor finds the root cause, read-only, with evidence for each claim. In our benchmark of 50 live faults across six tools, Radar found the most root causes. Radar Cloud investigates every alert and posts findings to Slack.
Replies
The read-only-until-approved default is the right way to let an agent near a cluster. On the 50-fault benchmark, did the six misses cluster around one failure type, or were they just noise?
@christian__schneider not noise - but not exactly one specific type. it was generaly things that are very hard to observe from k8s objects alone, and need some deeper inspection of the workload. e.g. read something broken with the DB auth, or some env var that changed when loaded via file, when there's not even a failing workload per se. Things that are really not "oh this pod has crashloopbackoff". You can see more details in radarhq.io/benchmark and the source for these scenarios in sregym.com