TGViewer
DevOps & SRE notes DevOps & SRE notes @devops_sre_notes · 13.3K subscribers
Post #2616 3.53K
Anyone who has been on call at night knows that it's impossible to react within minutes and triage an incident fast enough, especially if you are in such cases very rarely. When you are paged once a quarter or a year, all your dashboards are outdated, your diagnostic skills are lacking, and your understanding of the system has already changed a great deal. In those cases, a current AI agent can be useful. Looking at these article, I see that by the time you get paged, wake up, turn on your laptop, and try to open your eyes, the agent can already triage the incident and provide a full report with recommendations. Yes, we still need a human to approve those changes or do them manually (as with planes, people prefer to see a live human pilot, but autopilots are already better than humans).

https://www.opsworker.ai/blog/agent-driven-sre-investigations-a-practical-deep-dive-into-multi-agent-incident-response/
Blog | OpsWorker.ai — Insights on AIOps & AI SRE Automation Multi-Agent Incident Response: A Practical SRE Deep Dive | OpsWorker.ai A team of AI SRE agents is investigating Kubernetes incidents using k8s & GitHub MCPs to find root causes and create remediation pull requests.
  • 👍 5
  • 🔥 2
  • 👎 1
  • 🎉 1
More from @devops_sre_notes
  1. Sep 25, 2026Post #2750
  2. Sep 24, 2026Post #2749
  3. Sep 23, 2026Post #2747
  4. Sep 22, 2026Realtime log viewer with web UI, tail -f for logs with a web interface browser. https://gi…
  5. Sep 21, 2026Securing every Kubernetes workload at scale — LinkedIn Engineering https://www.linkedin.co…
  6. Sep 18, 2026Validate environment variable usage in codebase https://github.com/Chrilleweb/dotenv-diff
Threads Profile ViewerView any public Threads profile without an account.Open ThreadLook →Writing with AI? Make it sound human.Metric37 rewrites AI drafts so they read naturally. Free AI detector, 1,500 words free.Try Metric37 →