Design: What data is important during a fire fight and how do users configure alerts?

What do we want to learn and why?

Users need a way to configure incident issues in GitLab. Incidents will contain pertinent alert data, metrics visualizations. Incidents need to be automatically categorized and routed to the correct people/teams. We can do this by leveraging quick actions and conditional logic enabled by a templating language.

We need to understand what data/information is important to Users during a fire-fight and how they configure/refine their alerts. This will inform...

• What they want to include in their incidents
• How they want to format incidents
• What parameters they want to include in the incidents (are alerts the only source we need to consider?)
• Where we need to enable use of this templating language

Intended users

Sasha the Software Developer
Devon the DevOps Engineer
Sidney the Systems Administrator

Outcome

Results of this discovery issue will inform how we design issue templating with alert parameter and which templating language we select.