3h ago · 9 min read · An AI on-call agent is only as good as what it watches. That's what the rules system is for. Nightwatch's Watcher doesn't hardcode what to alert on. Instead, ops teams define rules in a single YAML f
Join discussion
3h ago · 10 min read · In Part 1, we built the skeleton of an AI on-call agent. Today we give it eyes. A multi-agent system that can't see your infrastructure is just a very expensive chatbot. So in this article we're repl
Join discussion
2d ago · 4 min read · In a monolithic application, tracking down a bug usually means logging into one server and running tail -f var/log/app.log. But in a Kubernetes cluster with hundreds of ephemeral pods constantly movin
Join discussion
3d ago · 10 min read · It's 3:07am. Your phone is screaming. The dashboard is red. You don't even remember what service checkout-orchestrator-v2 does. Welcome to on-call. Every backend engineer has a war story like that on
Join discussion
3d ago · 12 min read · Main blog: https://anshumanbiswal.com/2026/05/16/from-waterfall-to-aiops-the-evolution-of-devops-and-the-future-of-intelligent-operations/ Introduction There was a time when software delivery teams s
Join discussion6d ago · 13 min read · Key Takeaways Automated post-mortem generation is the process of producing an incident retrospective from artifacts already collected during the incident — chat transcript, alert timeline, monitor d
Join discussion
