<p>A prime use-case for Enterprise IT would be to reinvent their process for <strong>handling Major Incidents</strong> (sometimes called "Incident War-room") by utilizing the ChatOps practice.
I've captured this and additional use-cases relevant to Enterprise IT - in a blog series: </p>

<p><a href="https://community.hpe.com/t5/IT-Operations-Management-ITOM/ChatOps-ChatBots-and-Enterprise-IT/ba-p/6924240" rel="nofollow noreferrer">https://community.hpe.com/t5/IT-Operations-Management-ITOM/ChatOps-ChatBots-and-Enterprise-IT/ba-p/6924240</a></p>

<p><a href="https://community.hpe.com/t5/IT-Operations-Management-ITOM/Chat-Bots-in-the-Enterprise-Part-2/ba-p/6925811" rel="nofollow noreferrer">https://community.hpe.com/t5/IT-Operations-Management-ITOM/Chat-Bots-in-the-Enterprise-Part-2/ba-p/6925811</a></p>

<p>(and you can also continue to the 3rd part in that series from those links...)</p>

<p>I'd love to get your comments/feedback.</p>

CC BY-SA 3.0
2017-03-28T07:29:20.573Z
How about including the relevant parts from it in your answer? So that if those links ever stop working, your answer doesn't loose value.
Pierre.Vriens
CC BY-SA 3.0
2017-03-28T07:14:41.760Z
2017-03-28T07:14:41.760Z
Oded Zilinsky
<p>ChatOps is an absorbing topic; practically it means something very different to each team using it.  So much so that Atlassian have put together what could be considered to be a <a href="https://blog.hipchat.com/2016/02/05/chatops-guide-evolution-adoption-significance/" rel="noreferrer">Chat maturity model</a>.</p>

<ol>
<li><strong>Sputnik</strong>: Trying chat out to see how it works.</li>
<li><strong>Mercury</strong>: Starting to move to chat.</li>
<li><strong>Gemini</strong>: Chat as the primary source of communication, experimenting with bots.</li>
<li><strong>Apollo</strong>: Chat as the nexus of communication and work, including bots.</li>
<li><strong>Elon Musk</strong>: Chat is the primary centre of mission critical work.</li>
</ol>

<p><strong>Important:</strong> Chat and ChatOps is very specific to an organisation, think of Chat as the Fabric for your team's bots to existing within it's the bots that provide the functionality that enables business and technical processes.</p>

<p>With the brief lesson in ChatOps Theory over I can talk about the experiences that I have had with ChatOps:</p>

<h2>DevOps Support</h2>

<p><a href="https://slack.com/" rel="noreferrer">Slack</a> and <a href="https://www.pagerduty.com/" rel="noreferrer">PagerDuty</a> has fantastic integration allowing any newly raised incidents in PagerDuty then posted in one or more Slack Channels with information about the incident and buttons for acting upon the knowledge:</p>

<p><a href="https://i.sstatic.net/iYvna.png" rel="noreferrer"><img src="https://i.sstatic.net/iYvna.png" alt="PagerDuty in Slack"></a></p>

<p>Beyond connecting PagerDuty and Slack we also connected all of our monitoring and alerting tools into Slack so that it was the central point for all real and potential problems, including the ability to query <a href="https://newrelic.com/" rel="noreferrer">New Relic</a> directly from Chat.</p>

<h2>Chat as the Modern Command Line</h2>

<p>With another client we built custom bots that executed scripts on remote machines, we did this using a combination of calling the management APIs in Azure and running <a href="http://moo.nac.uci.edu/~hjm/clusterfork/" rel="noreferrer">Cluster Fork</a> commands:</p>

<blockquote>
  <p><code>@checky scale serviceA 30</code>: Scale ServiceA to 30 machines.</p>
  
  <p><code>@checky kill serviceA#4</code> : Kill instance number for on ServiceA.</p>
  
  <p><code>@checky exec serviceA#1,5 ps -awx</code> : run the <code>ps</code> command on serviceA instances 1 and 5 and post the output to chat</p>
</blockquote>

<h2>StackOverflow Close Vote Reviewers</h2>

<p>We have some chatbots running in the <a href="http://chat.stackoverflow.com/rooms/41570/so-close-vote-reviewers">SOCVR</a> channels that help us to:</p>

<ul>
<li>Find questions that need close votes.</li>
<li>Identify comments that contain "Heat" - i.e. might be offensive or lead to escalations.</li>
<li>Identify questions that are of poor quality that might need review.</li>
</ul>

<h2>Further Reading</h2>

<ul>
<li><a href="https://www.pagerduty.com/blog/what-is-chatops/" rel="noreferrer">So, What is ChatOps? And How do I Get Started?</a></li>
<li><a href="https://victorops.com/blog/new-chatops-book/" rel="noreferrer">VictorOps / O'Reilly ChatOps Book</a></li>
<li><a href="https://www.reddit.com/r/chatops/" rel="noreferrer">ChatOps Reddit</a></li>
<li><a href="http://cog-book.operable.io/index.html" rel="noreferrer">The Cog Book</a></li>
</ul>

CC BY-SA 3.0
2017-03-26T19:13:43.483Z
2017-03-26T19:20:09.987Z
2017-03-26T19:20:09.987Z
Richard Slater
<p>Many "simple" use cases shown in examples of ChatOps approach, creation of cloud instances, deployments to test environment etc., are there any use cases for production infrastructure management?</p>

<toolchain><infrastructure-as-code><chatops>
What are ChatOps approach use cases of production infrastructure management?
rombob
# What are ChatOps approach use cases of production infrastructure management?

(Asked by: username_0 on 2017-03-26)

Many "simple" use cases shown in examples of ChatOps approach, creation of cloud instances, deployments to test environment etc., are there any use cases for production infrastructure management?

**Tags:** toolchain, infrastructure-as-code, chatops


---

## 2 answers

### Answer by username_3 on 2017-03-26. Score: 7 | Accepted answer

ChatOps is an absorbing topic; practically it means something very different to each team using it. So much so that Atlassian have put together what could be considered to be a [Chat maturity model](https://blog.hipchat.com/2016/02/05/chatops-guide-evolution-adoption-significance/).

1. **Sputnik**: Trying chat out to see how it works.
2. **Mercury**: Starting to move to chat.
3. **Gemini**: Chat as the primary source of communication, experimenting with bots.
4. **Apollo**: Chat as the nexus of communication and work, including bots.
5. **Elon Musk**: Chat is the primary centre of mission critical work.

**Important:** Chat and ChatOps is very specific to an organisation, think of Chat as the Fabric for your team's bots to existing within it's the bots that provide the functionality that enables business and technical processes.

With the brief lesson in ChatOps Theory over I can talk about the experiences that I have had with ChatOps:

## DevOps Support

[Slack](https://slack.com/) and [PagerDuty](https://www.pagerduty.com/) has fantastic integration allowing any newly raised incidents in PagerDuty then posted in one or more Slack Channels with information about the incident and buttons for acting upon the knowledge:

[![PagerDuty in Slack](https://i.sstatic.net/iYvna.png)](https://i.sstatic.net/iYvna.png)

Beyond connecting PagerDuty and Slack we also connected all of our monitoring and alerting tools into Slack so that it was the central point for all real and potential problems, including the ability to query [New Relic](https://newrelic.com/) directly from Chat.

## Chat as the Modern Command Line

With another client we built custom bots that executed scripts on remote machines, we did this using a combination of calling the management APIs in Azure and running [Cluster Fork](http://moo.nac.uci.edu/~hjm/clusterfork/) commands:

> `@checky scale serviceA 30`: Scale ServiceA to 30 machines.
>
> `@checky kill serviceA#4` : Kill instance number for on ServiceA.
>
> `@checky exec serviceA#1,5 ps -awx` : run the `ps` command on serviceA instances 1 and 5 and post the output to chat

## StackOverflow Close Vote Reviewers

We have some chatbots running in the [SOCVR](http://chat.stackoverflow.com/rooms/41570/so-close-vote-reviewers) channels that help us to:

* Find questions that need close votes.
* Identify comments that contain "Heat" - i.e. might be offensive or lead to escalations.
* Identify questions that are of poor quality that might need review.

## Further Reading

* [So, What is ChatOps? And How do I Get Started?](https://www.pagerduty.com/blog/what-is-chatops/)
* [VictorOps / O'Reilly ChatOps Book](https://victorops.com/blog/new-chatops-book/)
* [ChatOps Reddit](https://www.reddit.com/r/chatops/)
* [The Cog Book](http://cog-book.operable.io/index.html)


---

### Answer by username_1 on 2017-03-28. Score: 2

A prime use-case for Enterprise IT would be to reinvent their process for **handling Major Incidents** (sometimes called "Incident War-room") by utilizing the ChatOps practice.
I've captured this and additional use-cases relevant to Enterprise IT - in a blog series:

<https://community.hpe.com/t5/IT-Operations-Management-ITOM/ChatOps-ChatBots-and-Enterprise-IT/ba-p/6924240>

<https://community.hpe.com/t5/IT-Operations-Management-ITOM/Chat-Bots-in-the-Enterprise-Part-2/ba-p/6925811>

(and you can also continue to the 3rd part in that series from those links...)

I'd love to get your comments/feedback.

> **Comments:**
> **username_2**: How about including the relevant parts from it in your answer? So that if those links ever stop working, your answer doesn't loose value.  

---

