1. Home
  2. Integrations
  3. Slack App Integration Guide – VictorOps

Slack App Integration Guide – VictorOps

Requirements

  • Slack Account: May Require Slack Administrative Privileges (in Slack this is called Primary Owner) to Integrate
  • VictorOps Version Required: Getting Started, Essentials, or Full-Stack
  • What You Need to Know:
    • At this time, Private Slack channels are not supported by this integration.
    • You must disable the old Slack (webhook) integration prior to enabling this one.
    • Multi-channel configuration requires Full Stack level of service and is described HERE

The VictorOps Slack App allows you to work on the platform of your choice without losing any functionality or information. You may now ACK or RESOLVE from your Slack channel of choice. The following guide will walk you through setting up this integration.


Before Getting Started

If you had previously installed our legacy Slack (webhook) integration you will need to disable the integration to prevent double messages from being sent between the two systems.

To do this, select the Slack (webhook) integration from the integrations page.

And then select Disable to revoke the integration.


Transfer of Ownership in Slack

Please be sure to recognize the administrative rights of your Slack environment. If you are not the Primary Owner of your Slack workspace you will need to seek out permission to transfer ownership in order to integrate with VictorOps.

These permissions may be managed in Slack under the main settings >> Manage Members.

Then, Transfer Ownership to the user tasked with the integration.

Primary Ownership may be easily transferred back to the original owner once the integration is complete.


In VictorOps

From the VictorOps web portal select Settings then Alert Behavior, then Integrations.

Next, select the Slack integration tile.

Then select Enable Integration.

This will bring up a Slack authentication screen to first pick the team you want to integrate with and then to log in.

Then, enter your email and password.

 

 

Next, Authorize the application.

Once authorized, you’ll be prompted to select a Slack channel.

Finally, you’ll be redirected back to VictorOps and a message will display that the Authentication was successful.


VictorOps web interface Settings

Now, from the VictorOps web interface, you may configure aspects of the integration. For instance, you may choose a Slack channel you’d like to integrate with and control the message notifications from VictorOps to Slack.

After you finish configuring your settings please be sure to press the Save button.


In Slack Channel

Invite The VictorOps Bot To The Channel

In Slack @ mention the @VictorOps bot user to add it to your channel if it doesn’t automatically appear.


Linking Your Slack User to your VictorOps User

From Slack, you can use the slash command /linkusers to generate a link that will initiate the linking process. You may also trigger a test alert from VictorOps to Slack. The action of attempting to ACK the incident in Slack will prompt the link.

Below, please find that attempting to ACK a triggered test incident will also prompt the user link to appear.

After selecting the link, log into your VictorOps account and you will be notified that your user is linked.

Once you’re connected you’ll be able to ACK the test incident in Slack.


Unlinking Slack Users from VictorOps

In the event that you need to unlink your VictorOps user from your Slack user, please contact VictorOps Support (support@victorops.com). This is a simple and quick process, but currently, it must be initiated by our support team.


Ack and Resolve in Slack

Now that your user is linked you can interact with VictorOps incidents from the slack channel.

In the VictorOps Timeline, you’ll be notified of Ack and Resolve actions that occurred in Slack.


Multi-Channel Configuration with Slack App

This configuration leverages our custom VictorOps Outgoing Webhooks and the Transmogrifier to send routing_key incidents to specified channels in Slack.  Please find our new documentation for multi-channel HERE.


Surfacing Annotations in Main Slack Channel

If you’ve purchased the VictorOps Full-Stack level of service, you may leverage our Transmogrifier and our custom Outgoing Webhooks to surface in Slack annotations associated with specific incidents.

Please see the example Webhook with attachments array below. In this example, the “title” field carries the clickable link and the “image_url” is, of course, the rendered image as defined in the Transmogrifer.

Webhook example:

You may copy and paste the below example directly into an Outgoing Webhook and edit the channel name, title, image_url, and color fields to suit your needs.

1
2
3
4
5
6
7
8
9
10
11
12
13
{
 "channel": "#general",
 "username": "VictorOps",
 "icon_url": "https://victorops.com/assets/img/branding/logo-yellow-mark.png",
 "attachments": [
 {
 "fallback":"What this image is in case it wont render",
 "title": "https://en.wikipedia.org/wiki/Australian_Cattle_Dog",
 "image_url": "http://i.dailymail.co.uk/i/newpix/2018/04/21/05/4B606CDA00000578-0-image-a-32_1524284530816.jpg",
 "color": "danger"
 }
 ]
}

Transmogrifer Annotation:

Annotation Appearance in VictorOps Incident Pane:

Annotations Appearance with Triggered Alert in Slack:

For further reference on attaching content and links to Slack via webhook, please read the Slack documentation on the subject found here.

If you have any questions regarding the above article, please contact VictorOps support (support@victorops.com).

Updated on October 12, 2018

Was this article helpful?

Related Articles