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

Slack Integration Guide – VictorOps

The VictorOps and Slack integration centralizes communication for engineers, developers, and IT managers. The Slack integration bridges the communication gap betlween on-call incident response and remediation to improve collaboration and reduce MTTR.

This guide contains the latest documentation for the current Slack integration with VictorOps, including both general and multi-channel configuration, as well as legacy documentation for webhooks integration.

Helpful Links:

Download the Slack App for VictorOps

Download the VictorOps App for Android (Mobile Only)

Download the VictorOps App for iOS

About Slack and VictorOps

Slack is an established leader in the communication and collaboration space. Whether you belong to a small business or a large enterprise, the VictorOps and Slack integration allows you to connect the people, tools, process, and automation into a transparent workflow.

    • Get monitoring, alerting, and chat data in one centralized location without disrupting incident workflows
    • The VictorOps and Slack integration allows you to see the full incident Payload, Acknowledge and Resolve issues, tag applicable teammates, and escalate alerts–all in one place
    • Collaborate around chat and incident Payload information at the same time
    • The two-way VictorOps and Slack integration captures all channel activities and lets you build reports to capture an entire history of incident activity

General Requirements

      • Slack Account: May Require Slack Administrative Privileges (in Slack this is called Primary Owner) to Integrate
      • VictorOps Version Required: Getting Started, Essentials, or Enterprise.
      • What You Need to Know:
        • You must disable the old Slack (webhook) integration prior to enabling this one.
        • Multi-channel configuration is available for all levels of service.

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.

Slack Multi-Channel Configuration – General Use

Configuration Requirements

Slack Account: May Require Slack Administrative Privileges (in Slack this is called Primary Owner) to Integrate Incoming Webhooks

Supported VictorOps Versions: Getting Started, Essentials, & Enterprise

Before Enabling

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.Disable Slack webhook integration

And then select Disable to revoke the integration.


Transfer 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.

VictorOps Slack transfer of ownership

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

VictorOps transfer of ownership form

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


Configure VictorOps

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

selecting integrations in victorops

Next, select the Slack integration tile.

selecting slack integration in victorops

Then select Enable Integration.enabling slack integration in victorops

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

signing in to your slack instance in victorops

Then, enter your email and password.

 

email and password prompt for slack integration victorops

 

Next, Authorize the application.

authorize slack integration in victorops

If you’ve already integrated Slack with VictorOps, you’ll be prompted on your Slack integration settings page to upgrade to Slack v2.3.

upgrade slack integration in victorops

Once you’ve updated the integration you’ll be able to Add Mapping between VictorOps Escalation Policies and Slack Channels. Initially, you’ll be prompted to pick a default Slack channel.

Add Mapping between VictorOps Escalation Policies and Slack Channels

Once you’ve Added Mapping you’ll be able to select from a list of existing Escalation Polices and Slack Channels, as well as define settings to individual Slack Channels for more granular functionality. Private channels work as well.

select from a list of existing Escalation Polices and Slack Channels

Toggling on and off the Channel Settings check boxes are good way to limit noise and control information flow into specific channels.

You may also map multiple Escalation Policies to Slack Channels.

map multiple Escalation Policies to Slack Channels.

When mapping private Slack channels you must give the VictorOps app permission to post to your private Slack channel. First, map your Escalation Policy to your desired private Slack channel.

give the VictorOps app permission to post to your private SlackNext, head over to Slack and in your private Slack channel @mention VictorOps or select ‘Add an app’.

mention VictorOps or select 'Add an app'

Finally, give the app permission by selecting ‘Invite Them’.

give the app permission by selecting 'Invite Them' slack victorops

Now, the VictorOps app will be able to post to your private channel.


Configure Slack

Triggered VictorOps incidents will route to specified Slack Channels based on Escalation Policy. From Slack you may Acknowledge, Reroute, Resolve, and even Snooze incidents.

Triggered VictorOps incidents route to specified Slack Channels

Slack Slash Commands

Currently, there are three Slack slash commands that work with VictorOps:

/victor-linkuser

/victor-unlinkuser

/victor-createincident

(Please note: when using this command please be sure to use the full syntax including brackets. For example:

/victor-createincident [make sure you use the correct syntax] for [victorops username]

three Slack slash commands that work with VictorOps

 

Tips & Tricks

To keep communication about an incident all in one place, use a hashtag and the incident number to reference a specific incident within Slack.

use a hashtag and the incident number to reference a specific incident within Slack VictorOps

The message that contains this hashtag will then appear in the relevant incident’s timeline:

message containing hashtag appears in the relevant incident's timeline victorops

 

If you need to enable the integration, if you have any feedback or if you need to report an issue with the Slack integration, please don’t hesitate to reach out to us at victorops-support@splunk.com.

 


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.

VictorOps example webhook with attachment array

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

Transmogrifier Annotation

Annotation Appearance in VictorOps Incident Pane:

Annotation appearance in VictorOps incident pane

Annotations Appearance with Triggered Alert in Slack:

Annotation 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).

 

 

Multi-Channel Configuration via Webhooks

Requirements

Slack Account: May Require Slack Administrative Privileges (in Slack this is called Primary Owner) to Integrate Incoming Webhooks

VictorOps Version Required: Enterprise

What you need to know:  This Slack multi-channel configuration is to be used with VictorOps Custom Outgoing Webhooks and our Slack App integration. To avoid confusion, this configuration is NOT to be used with our legacy Slack (Webhook) integration. We recommend using this documentation with our standalone Slack App integration.

Currently, in this multi-channel configuration, bi-directionality is not supported outside of the main VictorOps Slack App channel. This configuration is VictorOps to Slack only.

Custom Outgoing Webhooks Configuration Overview

This setup allows you to segregate VictorOps incidents into their own separate Slack channels based on the routing_key value in VictorOps. Incident-specific chats in VictorOps (chats entered into the incident-pane chat bar on the far right) may also be sent to a specific Slack channel based on the routing_key of the incident. This configuration adds the name of the VictorOps user that Ack’d and Resolved the incidents, and provides links in Slack that take the user directly to the incidents in VictorOps.

In the following document, we’ll show you how to configure the Slack App for Incoming Webhooks, create VictorOps Outgoing Webhooks, and create new Transmogrifier rules to help steer VictorOps incidents and chats into specified Slack channels.


Custom Config in Slack

Within Slack, in Slack’s App Directory, you’ll want to add as a configuration Incoming WebHooks.

add as a configuration Incoming WebHooks

Next, create a new Incoming Webhook. Here, under Integration Settings, you’ll want to Post to your main VictorOps Slack channel. This is the Channel that’s declared in the VictorOps Slack App integration page. You’ll also want to copy the Webhook URL and save it for use when we set up the VictorOps custom Outgoing Webhooks.

create a new Incoming Webhook with Victorops

Now that we’ve copied the correct Webhook URL and have the appropriate Slack channel selected, we’re ready to head over to VictorOps for further configuration.


Custom Config in VictorOps

Within VictorOps you’ll want to leverage our custom Outgoing Webhooks and our Transmogrifer to steer VictorOps incident, shift change, and chat activity to designated channels in Slack.


Transmogrifier Rules

In VictorOps, click Settings >> Alert Behavior >> Transmogrifier, then click the Add a Rule.  (In all cases you will leave the Stop after this rule has been applied UN-CHECKED)

In VictorOps, click Settings >> Alert Behavior >> Transmogrifier, then click the Add a Rule.

 

The first rule will add the slugified version of your organization name (org slug) to all incidents. When you are logged into the main VictorOps timeline, your org slug is located at the end of the URL. For example, if the URL is https://portal.victorops.com/client/my-company, then the org slug, in this case, is “my-company”.  For the matching condition, alert field = * (star to catch all incidents based on entity_id). For the Transform, alert field = org_slug AND new value = (your org slug here)  like so:
add the slugified version of your organization name (org slug) to all incidents VictorOps

Click Save once complete!

Now you will create rules to associate your Slack channels to their appropriate routing_keys in VictorOps.  In this example, the routing key I want to use is “ops” and the name of the Slack channel I wish to link is “support”.  Click Add a Rule.  For the matching condition, alert field = routing_key AND pattern = (Your routing_key here).  For the Transform, alert field = slack_channel AND new value = (Slack channel name here) like the example below.  Do not include a # sign before the channel name.

create rules to associate your Slack channels to their appropriate routing_keys in VictorOps

If you have have many Slack channels and many routing keys, you will need one rule per VictorOps routing_key. In other words, configure one Transmogrifier rule per routing_key in order to send routed alerts to specific slack channels.


Outgoing Webhooks

Navigate to our custom Outgoing Webhooks: Settings >> Alert Behavior >> Outgoing Webhooks. Here you’ll want to create four outgoing webhooks based on Event Type. 

create four outgoing webhooks based on Event Type.

You will need a total of 4 webhooks to complete this setup. All four of these webhooks will use the same URL (the one we copied from Slack) in the “To Field:” You can copy and paste the templated payloads found below exactly as they are. If you would like to add more variables to your payload, see the ‘Available Variables’ column to the right of the payload. As long as you have the required Transmogrifer rules, no editing of the payload should be necessary.

configuring outgoing webhooks with VictorOps

Configure the following webhooks (you will have to click Add Webhook at the top each time, then scroll down to the new window).

1) Incident Chats to Slack:

  • Event: Incident-Chats
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 8 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
{ 
    "channel": "#${{ALERT.slack_channel}}",
    "username": "VictorOps Chat (${{CHAT.USER_ID}})",
    "icon_url": "https://victorops.com/assets/img/branding/logo-yellow-mark.png", 
    "attachments": [{ 
        "text": "${{CHAT.TEXT}} \n <https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>", 
        "color": "#4dc3ff",
        "mrkdwn_in": ["text"] 
        }]
}
  • Description:  Send incident chats to their appropriate Slack channel

2) Critical Incidents to Slack:

  • Event: Incident-Triggered
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
12
13
{
   "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
   "attachments": [
        {
          "title":"CRITICAL INCIDENT TRIGGERED",
          "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
          "color":"danger",
          "mrkdwn_in": ["text"]
        }
    ]
}
  • Description: Send triggered incidents to their appropriate Slack channel

3) Acknowledgements to Slack:

  • Event: Incident-Acknowledged
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
{ 
    "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
    "attachments": [ { 
        "title":"ACKNOWLEDGED by ${{STATE.ACK_USER}}",
        "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
        "color":"warning",
        "mrkdwn_in": ["text"] 
        } ] 
}
  • Description: Send incident acknowledgments to their appropriate Slack channel

4) Recoveries to Slack:

  • Event: Incident-Resolved
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
12
13
{
   "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
   "attachments": [
        {
          "title":"RESOLVED by ${{STATE.ACK_USER}}",
          "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
          "color":"good",
          "mrkdwn_in": ["text"]
        }
    ]
}
  • Description: Send incident recovery events to their appropriate Slack channel

End Result in Slack

Back in Slack, each channel should see incident activity (based on routing key) for the four configured webhooks. As you can see, in the below image there’s a incoming Triggered event, Acknowledged event, Resolved event, and a Chat.

incoming Triggered event, Acknowledged event, Resolved event, and a Chat

Legacy Slack Integration Guide

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.

finding Transfer Ownership link

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

VictorOps Transfer Ownership module

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.

Victorops Settings - Alert Behavior - Integrations selection

Next, select the Slack integration tile.

VictorOps - Finding Slack on Integrations Module

Then select Enable Integration.selecting enable integration - slack and victorops

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

slack authentication screen on victorops

Then, enter your email and password.

 

email and password prompt for integration screen

 

Next, Authorize the application.

integration authorization - slack and victorops

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

choosing a slack channel - slack victorops integration

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

authentication success - slack victorops integration


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.

Saving your settings - VictorOps Slack integration


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.

In slack - invite the bot


Linking Your Slack User to your VictorOps User

From Slack, you can use the slash command /linkuser to generate a link that will initiate the linking process.

using linkuser command to lick slack with victorops

After running the /linkuser command, log into your VictorOps account and you will be notified that your user is linked.

Once you’re connected you’ll be able to successfully ACK incidents in Slack. Note: If you do not link your user, incident actions in Slack will not be passed to VictorOps.


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.

Victorops Slack test incident 1

VictorOps Slack alert incident example 2

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

VictorOps timeline slack notification

Legacy Webhooks Integration

Requirements

Versions Supported: Slack 2.x

VictorOps Version Required: Getting Started/Essentials (Basic config), Enterprise (Multi-Channel config).

What you need to know The basic configuration links your VictorOps timeline, bidirectionally, to a single Slack channel. The advanced configuration provides links and routing to multiple Slack channels with some limitations (must complete basic setup first).

Before we get started, please note that this integration is not the recommended Slack integration. We recommend integrating with the Slack App integration listed under the General Use section of this document. The newest iteration of our Slack integration provides more functionality within Slack.

Basic Webhooks Configuration

Enable the Integration

(You must be an admin user in VictorOps)
1. From the VictorOps Timeline select “Settings” >> “Alert Behavior” >> “Integrations”.

2. Scroll down and select the “Slack (webhook)” integration button (alphabetical order).  If the integration has not been enabled, click “Enable Integration”.

3. Copy the Outgoing Webhook URL that is generated by enabling the integration, and keep this page open as you will return to paste in the webhook URL generated by Slack in subsequent steps.

Webhooks: VictorOps to Slack

4. From your Slack account (as an Admin) navigate to the channel you wish to link and select the settings icon. Choose to Add an app or integration.

5. In the search function, type “webhooks” and select Incoming WebHooks

6. Click on Add Configuration

7. Select the channel you want to link to your VictorOps timeline.

8. Copy the Webhooks URL to your clipboard.

9.Scroll to the bottom and click Save Settings.

10. Paste the URL into the Incoming Webhook URL section. (It saves automatically, nothing more to click)


Webhooks: Slack to VictorOps

11. Return to the Slack integrations search function, and type “webhooks”.  Select Outgoing WebHooks.

12. Click on Add Configuration.

13. Click Add Outgoing WebHooks Integration.

14. Scroll down to the Integration Settings section.  Select the channel you are linking with VictorOps and then paste the URL you copied from the Outgoing Webhooks URL section in VictorOps (Step 3 above) into the URL(s) section in Slack.

15. Scroll to the bottom and select Save Changes.


Configure and Test

16. Return to the Slack integration settings in VictorOps and read through the Slack Options section to fine tune the integration.

17.  Navigate to your main timeline in VictorOps, and enter any text into one of the two chat bars and press ENTER/RETURN. (Notice that the chat bar located in the incident pane (far right) will append the incident # to the chat)  You should see the chat appear in your Slack channel.  Reply to the chat from within Slack and you should see the response in the VictorOps timeline.


Legacy Multi-Channel Configuration

This setup allows you to segregate VictorOps incidents into their own separate Slack channels based on the routing_key value in VictorOps.  Incident-specific chats in VictorOps (chats entered into the incident-pane chat bar on the far right) can also be sent to a specific Slack channel based on the routing_key of the incident.  This setup also adds the name of the VictorOps user that ack’d and resolved incidents, as well as links in Slack that take the user directly to the incident in VictorOps.


Important Considerations:

  • This is not the recommended multi-channel configuration. This is legacy documentation for multi-channel configuration within our legacy slack integration.
  • This setup requires the Enterprise version of VictorOps to make use of the Transmogrifier and Custom Outgoing Webhooks features.
  • You must have configured routing keys in VictorOps for each of the teams you wish to associate with a Slack channel. (Settings >> Integrations >> Scroll to bottom)
  • Note: The names of the Slack channels will be declared directly in the payload of the webhooks to Slack, therefore you can use the same URL from step 8 of the basic setup.
  • In order to prevent duplicate events in your Slack channel, you may need to change your Slack integration settings in VictorOps.  (De-select the options that send incidents and/or chats into Slack)

slack18


Transmogrifier Rules

1. In VictorOps, click Settings >> Transmogrifier, then click the Add a Rule.  (In all cases you will leave the Stop after this rule has been applied UN-CHECKED)

2. The first rule will add the slugified version of your organization name (org slug) to all incidents.  When you are logged into the main VictorOps timeline, your org slug is located at the end of the URL (Ex. if the URL is https://portal.victorops.com/client/my-company, then the org slug, in this case, is “my-company”).  For the matching condition, alert field = * (star to catch all incidents). For the Transform, alert field = org_slug AND new value = (your org slug here)  like so:

Click Save once complete.

3. Now you will create rules to associate your Slack channels to their appropriate routing_keys in VictorOps.  In this example, the routing key I want to use is “ops” and the name of the Slack channel I wish to link is “support”.  Click Add a Rule.  For the matching condition, alert field = routing_key AND pattern = (Your routing_key here).  For the Transform, alert field = slack_channel AND new value = (Slack channel name here) like the example below.  Do not include a # sign before the channel name.

You will need another rule like this for each of the VictorOps routing_keys you wish to link to a Slack channel.


Outgoing Webhooks

You will need a total of 4 webhooks to complete this setup.  You can copy and paste the payloads below exactly as they are.  As long as you have set up the Transmogrifier rules, no editing of the payload should be necessary.

4. In VictorOps, navigate to Settings >> Webhooks and click on Add Webhook to create a new webhook.

5. Configure the following webhooks (you will have to click Add Webhook at the top each time, then scroll down to the new window)

Incident Chats to Slack:

  • Event: Incident-Chats
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 8 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
{ 
    "channel": "#${{ALERT.slack_channel}}",
    "username": "VictorOps Chat (${{CHAT.USER_ID}})",
    "icon_url": "https://victorops.com/assets/img/branding/logo-yellow-mark.png", 
    "attachments": [{ 
        "text": "${{CHAT.TEXT}} \n <https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>", 
        "color": "#4dc3ff",
        "mrkdwn_in": ["text"] 
        }]
}
  • Description:  Send incident chats to their appropriate Slack channel

Critical Incidents to Slack:

  • Event: Incident-Triggered
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
12
13
{
   "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
   "attachments": [
        {
          "title":"CRITICAL INCIDENT TRIGGERED",
          "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
          "color":"danger",
          "mrkdwn_in": ["text"]
        }
    ]
}
  • Description: Send triggered incidents to their appropriate Slack channel

Acknowledgements to Slack:

  • Event: Incident-Acknowledged
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
{ 
    "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
    "attachments": [ { 
        "title":"ACKNOWLEDGED by ${{STATE.ACK_USER}}",
        "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
        "color":"warning",
        "mrkdwn_in": ["text"] 
        } ] 
}
  • Description: Send incident acknowledgments to their appropriate Slack channel

Recoveries to Slack:

  • Event: Incident-Resolved
  • Method: POST
  • Content Type: application/json
  • To: (Your Slack URL from step 3 of the basic setup)
  • Payload:
1
2
3
4
5
6
7
8
9
10
11
12
13
{
   "channel":"#${{ALERT.slack_channel}}",
    "username":"VictorOps",
    "icon_url":"https://victorops.com/assets/img/branding/logo-yellow-mark.png",
   "attachments": [
        {
          "title":"RESOLVED by ${{STATE.ACK_USER}}",
          "text": "<https://portal.victorops.com/client/${{ALERT.org_slug}}#/incident/${{STATE.INCIDENT_NAME}}|*#${{STATE.INCIDENT_NAME}}*: ${{ALERT.monitoring_tool}}: ${{ALERT.entity_display_name}}>",
          "color":"good",
          "mrkdwn_in": ["text"]
        }
    ]
}
  • Description: Send incident recovery events to their appropriate Slack channel
Updated on April 24, 2019

Was this article helpful?

Related Articles