Send Alerts to Slack (#216326) · Issues · GitLab.org / GitLab

Send Alerts to Slack

Problem to solve

Slack is often used as a central communication platform where users are notified of alerts and incidents for their IT systems.

Intended users

Further details

This work drives the direction of the Alert Management category.

Proposal

Utilize the existing Slack notifications integration (visible off of Settings > Integrations > Slack notifications)
Introduce a new section at the end of the list called, Alerts:

We send a notification to Slack when a new alert record is created in GitLab. If multiple events come into GitLab for the same alert, we'd only send a single notification, for the first alert record we receive.
We could base the Slack notification on what we do for our existing generic endpoint alert notifications. We could also introduce some extra formatting to make it better align with the Slackline alert notifications:

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

### Problem to solve
Slack is often used as a central communication platform where users are notified of alerts and incidents for their IT systems.

### Intended users

* [Devon (DevOps Engineer)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#devon-devops-engineer)
* [Allison (Application Ops)](https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/#allison-application-ops)

### Further details

This work drives the direction of the [Alert Management](https://about.gitlab.com/direction/monitor/debugging_and_health/alert_management/) category.

### Proposal

*  Utilize the existing Slack notifications integration (visible off of Settings > Integrations > Slack notifications)
*  Introduce a new section at the end of the list called, Alerts:

![Screen_Shot_2020-05-07_at_12.48.56_PM](/uploads/3ae0d6dc6f092b2fd6ebdce25e5bdb6b/Screen_Shot_2020-05-07_at_12.48.56_PM.png)
*  We send a notification to Slack when a new alert record is created in GitLab. If multiple events come into GitLab for the same alert, we'd only send a single notification, for the first alert record we receive.
* We could base the Slack notification on what we do for our existing generic endpoint alert notifications. We could also introduce some extra formatting to make it better align with the Slackline alert notifications:

![Artboard](/uploads/3b0433a46a07cf4a634f71157441dce9/Artboard.png)

### Permissions and Security

### Documentation

<!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/workflow.html#for-a-product-change

* Add all known Documentation Requirements in this section. See https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements
* If this feature requires changing permissions, update the permissions document. See https://docs.gitlab.com/ee/user/permissions.html -->

### Availability & Testing

<!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier.

What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing?

Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance.
* Unit test changes
* Integration test changes
* End-to-end test change

See the test engineering planning process and reach out to your counterpart Software Engineer in Test for assistance: https://about.gitlab.com/handbook/engineering/quality/test-engineering/#test-planning -->

### What does success look like, and how can we measure that?

### What is the type of buyer?

### Is this a cross-stage feature?

### Links / references

Edited May 13, 2020 by Sarah Waldner

Discussion
Designs