Skip to content
GitLab
Next
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • GitLab GitLab
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46,648
    • Issues 46,648
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,516
    • Merge requests 1,516
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and 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.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #232492
Closed
Open
Issue created Jul 27, 2020 by Dimitrie Hoekstra@dimitrieh🔥Contributor0 of 6 checklist items completed0/6 checklist items

Allow for easier roll back from alerts page

Problem to solve

As an SRE, I want to take action on alert, so I can resolve it.

This is a continuation from #216949 and intended as a first iteration towards making it easier for SRE's to take action on alert.

Currently, an SRE when navigating towards an alerts page is missing context or the ability to easily see and act on deployments for the related environment.

Today, we don't show which environment is associated with the alert. e.g. https://gitlab.com/gitlab-org/monitor/tanuki-inc/-/alert_management/105/details doesn't show environment link. Thus, SREs have no idea which environment is having trouble.

Intended users

  • Sidney (Systems Administrator)

User experience goal

Allow the user to easily see and act on deployments for the related environment of an alert.

Proposal

Add environment name detail to front page of alert:

Browser mockup
image
  • Add link to environment

Add environment row under Alert details above Details:

Browser mockup
image

Further details

Permissions and Security

Documentation

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

Feature Flag

This feature is implemented behind graphql_expose_environment_path feature flag and disabled by default. Once we've confirmed the feature is deemed stable, we remove the feature flag in order to publish the feature as GA. Rollout Issue: #258638 (closed)

Weight

  • backend : Expose environment URL in the AlertManagement GraphQL endpoint.
  • frontend : Visualize the environment URL on the alert detail page.
  • backend : Publish the feature (documentation + feature flag removal)
Edited Sep 29, 2020 by Angelo Gulina
Assignee
Assign to
Time tracking