The documentation you're currently reading is for version 2.6.0. Click here to view documentation for the latest stable version.
ChatOps provides a new way of collaboration and work within your teams. Boiled down to its essence, ChatOps represents conversation-driven development. With ChatOps, it is possible to take operational and development workflows and expose them as commands that can be executed in a company chat room. In doing so, you are unifying the communication about what work should get done with the actual history of the work being done.
Deploying code from Chat, viewing graphs from a TSDB or logging tool, or creating new Jira tickets are all examples of tasks that can be done via ChatOps.
Not only does ChatOps reduce the feedback loop of work output, it also empowers others to accomplish complex, self-service tasks that they otherwise would not be able to do. Combining ChatOps and StackStorm is an ideal combination: from Chat users will be able to execute actions and workflows to accelerate the IT delivery pipeline. In the same way, the ChatOps/StackStorm combination also enhances user adoption of automation through transparency and consistent execution.
The end result is improved agility and enhanced trust between teams. What’s not to love about this? It’s the reason we as a company are devoted to including it as a core part of our product.
You’re busy. We get it! If you’ve installed EWC according to the instructions then you already have
st2chatops installed. It just needs configuring.
Jump to ChatOps configuration to see what to do. Follow those
steps, then keep reading to see what you can do!
Interested in learning more? Here are some things to get you started on your voyage.
- ChatOps: Technology and Philosophy
- Start automating with Slack
- Demonstration: See StackStorm and ChatOps in action
- ChatOps for Dummies, Published by VictorOps
- ChatOps and Event Driven Automation
- ChatOps on Reddit
- ChatOps on #freenode