Spike: Create a simple repeatable process by which customers can integrate any tool with GitLab
Overview
As stated in the parent epic, enterprises are already invested and entrenched in a suite of monitoring tools, moreover, there are hundreds of monitoring tools in market today. These emit alerts with unique payloads differing in format and content. GitLab's Alert Management tool needs to be able to consume and aggregate alerts from any tool. Other incident management tools have invested in building and maintaining individual integrations so that they can consume proprietary alerts from all of these tools.
This is not a viable solution for GitLab because:
- Our team focused on solving this problem in market is small (there are entire companies working on this)
- Building integrations with a large percentage of these tools will take too long because of 1
- Maintaining all of these integrations would be a lot of on-going work
To overcome these limitations, we need to create a simple repeatable process by which customers can integrate any tool with GitLab.
If we can create a service that transforms proprietary alerts into a single standard that can be sent to GitLab, we can quickly catch up to other incident management tools in market.
Purpose
Research and propose how we might enable Operations users to view & map fields from proprietary alerts to the gitlab required fields and save these are integrations.
The proposal must take into account the following:
Each of these integrations will have a unique endpoint and auth token. The reason for this is to protect the user from taking down all of their alerting in the scenario the auth token is compromised and needs to be reset. Resetting an auth token that is used for all alert integrations would immediately stop all alerting and force the user to have to log into each of these tools to replace the auth token.
Deliverable
Add findings and outline a plan for implementation in #217766 (closed)