Skip to content
GitLab
Next
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 44,761
    • Issues 44,761
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,332
    • Merge requests 1,332
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • 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
  • #219142
Closed
Open
Issue created May 26, 2020 by Amelia Bauerly@ameliabauerlyDeveloper

Moving alerts endpoint configuration to Settings > Operations

Problem to solve

Right now, users configure both Prometheus and Alerts Endpoints in Settings > Integrations. When #24651 (closed) is implemented in 13.2, Prometheus configuration will move to Settings > Operations. We should probably move the alerts endpoints configuration to Settings > Operations as well, to ensure that users don't have to go to two separate settings pages to configure alerts endpoints.

Intended Users

  • Allison (Application Ops)
  • Devon (DevOps Engineer)

Further details

This work supports the direction of the Alert Management product category.

Proposal

How this implementation will look will depend on where we are at with #214525 (closed) and how we want to break down work here.

Collapsed alert section on Settings > Operations Moving the alerts endpoint config to settings > operations before email integrations are introduced Moving alerts endpoint to settings > operations at the same time as we introduce email integrations Old settings page deprecated
Settings_page_-_collapsed Settings_page Settings_page_-expanded-_alert_endpoint Settings___Operations_Alert

The only difference between the two designs, is whether we are able to introduce the tabs yet...or not. If the email configuration piece isn't ready yet, we can just port the content from the alerts endpoint section over directly. If it is ready to be implemented, we can introduce the tabs straight away, and the alert endpoint configuration fields can be displayed in the first tab.

User experience goal

Ensure the config for alerts is as seamless as possible (and that users don't need to visit multiple settings pages to set it up)

Permissions and Security

Documentation

Documentation required. Please update 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 Sarah Waldner
Assignee
Assign to
Time tracking