ChatOps
A collaboration model that connects people, tools, and scripts into a transparent workflow (usually Slack/Teams).
A collaboration model that connects people, tools, and scripts into a transparent workflow (usually Slack/Teams).
## "Conversation-Driven Development" **ChatOps** pushes all your ops tools into the chat room. Instead of opening a terminal to run `deploy`, you type `/deploy` in Slack. ### Why do this? 1. **Visibility**: Everyone sees that you just deployed. No more "Who is touching prod?". 2. **Onboarding**: Juniors see exactly what commands Seniors are running. 3. **Mobile**: You can fix incidents from your phone. ### The Stack * **Chat Platform**: Slack, Microsoft Teams. * **Bot**: Hubot, Slack App. * **Infrastructure**: AWS, Kubernetes, PagerDuty. ### Common Commands * `/page on-call` (Pages the on-call person). * `/status` (Shows system status). * `/incident create` (Starts an incident and war room).
ExThe GitHub Way
"GitHub invented ChatOps. They deployed GitHub.com using a bot called Hubot for years."
Why ChatOps Matters
ChatOps brings incident management into the place where teams already work.
Running commands from chat (e.g., `/incident resolve`) ensures everyone sees what is happening in real-time.