### Problem to solve Charts help users visualize what went wrong while triaging alerts. If a particular threshold was exceeded, we can reduce time spent during investigation by automatically including the relevant metrics chart in the alert. ### 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) ### User experience goal Have metrics available as part of the alerts workflow, so users don't have to switch context and/or navigate elsewhere as part of the alert triage process. ### Proposal Allow users to view metrics as part of the alert triage workflow for alerts from GitLab managed Prometheus instances. To ensure the smallest possible iteration, we can use the same time-range behaviour as incident embeds - to center on the start-time and show 30 mins before and after: https://docs.gitlab.com/ee/user/project/integrations/prometheus.html#embedding-metrics-based-on-alerts-in-incident-issues ### Design We can introduce an additional tab to hold the metrics we receive (or are able to generate): | Loading state | Metric displayed | No metrics available (MVC) | | ------ | ------ | ------ | |  |  |  | ### Further details <!-- Include use cases, benefits, goals, or any other details that will help us understand the problem better. --> ### Permissions and Security ### Documentation Documentation required. Please add a new sub-section to [this section](https://docs.gitlab.com/ee/user/project/operations/alert_management.html#alert-management-details). ### 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? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://about.gitlab.com/handbook/product/pricing/#four-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### Links / references