Incident Management Gap Analysis, Infrastructure
Purpose
To complete the GitLab Infrastructure team's migration to Incident Management, the Monitor team is planning a 3 phased approach to iteratively fill in feature gaps in our Incident Management tooling. The first phase of the migration plan is to identify and fill main feature/fucntionality gaps. The purpose of this issue is to document and get sign off from the SRE on the feature gaps that are preventing the SRE from using GitLab for incident management.
Gap Analysis
Below is a list of functionality that is missing from GitLab (i.e. gaps) that is preventing the SRE from using GitLab for incident management.
| Sequence | Gap | Issue/Epic | Timing |
|---|---|---|---|
| 1. | Integrate alert sources | gitlab-org&4390 (closed) | 13.5, 13.6 |
Below is a list of functionality that is missing from GitLab (i.e. gaps) that is preventing the SRE from using GitLab as a potential replacement for paging tooling currently in use.
| Sequence | Gap | Issue/Epic | Timing |
|---|---|---|---|
| 1. | Manage on-call schedules & escalations | gitlab-org&3960 (closed) | 13.7, 13.8, 13.9 |
| 2. | Page on-call responders | gitlab-org&1438 | 13.8, 13.9 |