Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43,848
    • Issues 43,848
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,392
    • Merge requests 1,392
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #217768
Closed
Open
Created May 14, 2020 by Sarah Waldner@sarahwaldner🍉Developer

Surface metrics charts on the alert detail page for alerts from GitLab-managed Prometheus

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)
  • 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)
Metrics_-_loading Metrics_-_chart_displayed Metrics_-_possible_MVC_empty_state

Further details

Permissions and Security

Documentation

Documentation required. Please add a new sub-section to this section.

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited Jun 04, 2020 by Amelia Bauerly
Assignee
Assign to
Time tracking