This epic groups all epics that are required to move the Alert Management category from `planned` to `minimal`. The description of this epic is a summary of the [Opportunity Canvas](https://docs.google.com/document/d/1-sJoVFr3ND_-N3EtXUNYF6oVROfhE4rcjVqpnQd5N6U/edit). Please reference the canvas for a full evaluation of this project. ### Overview Processing alerts during a fire-fight requires responders to coordinate across multiple tools to evaluate different data sources. Collecting and assessing metrics, logs, and traces and sharing these with a response team involves screengrabs & copy/pasting data into a single ticket to aggregate the information, necessary for keeping a team up to date and stakeholders informed. All of this manual work is time-consuming and challenging which leads to alert fatigue, increased stress, and low morale. Over time team members will start to miss critical alerts due to the challenges that a distributed tool chain poses and the sheer volume of information that they need to consume to actually determine the root cause of incidents. In these scenarios, we see alerts discarded instead of leveraged as an important element in DevOps. ### Opportunity GitLab is uniquely positioned to become not only the place where companies manage and respond to alerts, but also where they remediate them. This is our differentiator. In order to become this Operations Command Center, we need build an interface that enables users to consume alerts from many different sources, correlate pieces of data, determine the point in code that is causing the problem, and quickly get a fix to production. #### Dogfooding Adding the end-to-end triage flow to GitLab that starts with a triggered alert at GitLab's REST endpoint and ends with a resolved incident issue, will be a major step towards enabling GitLab's SRE team to dogfood GitLab for triage and incident management workflows on ops.gitlab.net. We will be holding game-days as we mature Alert Management to test the functionality and gather feedback on improvements and new features efficiently. We plan to hold the first game day after we release Alert Management Minimal. The plan for the first game day can be viewed [here](https://gitlab.com/gitlab-org/monitor/health/-/issues/18). ### Minimal Strategy - What are we starting with? We will begin by making it simple to route your alerts to GitLab. Similar to how your application runs on a stack of technology, customers have a stack of monitoring tools to ensure each layer of your tech is reliable and available. There are hundreds of tools in market. We want to consume alerts from all of them. We are going to build an interface where users can view all of their alerts from different tools in a single interface and by clicking on an alert, they can view more details specific to that alert. **The `minimal` version of Alert Management will include:** * Alert list view - basic columns, can click on alert to get to the detail view * Alert detail view in plain text When we have built and released the functionality listed above, Alert Management will have matured to minimal. Please check out what is next for Alert Management Viable. ### Designs These are the designs we've defined as part of https://gitlab.com/gitlab-org/gitlab/-/issues/210766. Not everything that's pictured here will be part of the minimal version of Alert Management, as some of these features have been split into minimal and some into the viable epics. See issues included in each epic for details. | Initial empty state | Configuration screen (already exists in the UI - some copy updates) | Alerts list view | Alerts detail view | Alerts detail view - additional tab | Issue created from alert | | ------ | ------ | ------ | ------ | ------ | ------ | |  |  || |  | | [Sketch cloud link to all designs](https://sketch.cloud/s/aQkwZ) [Measure spec](https://gitlab-org.gitlab.io/gitlab-design/hosted/amelia/gl%23210766-design-discovery-surface-alerts-in-gitlab-spec-previews/) ### Bare Minimum Issues required to release as Alert Management Minimal - https://gitlab.com/gitlab-org/gitlab/-/issues/216065 - https://gitlab.com/gitlab-org/gitlab/-/issues/213876 - https://gitlab.com/gitlab-org/gitlab/-/issues/213880 - https://gitlab.com/gitlab-org/gitlab/-/issues/213892 - https://gitlab.com/gitlab-org/gitlab/-/issues/213911 - https://gitlab.com/gitlab-org/gitlab/-/issues/215103 (this one might be technically necessary, engineering to advise) - https://gitlab.com/gitlab-org/gitlab/-/issues/214518 - https://gitlab.com/gitlab-org/gitlab/-/issues/214624 - https://gitlab.com/gitlab-org/gitlab/-/issues/214625