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,331
    • Merge requests 1,331
  • 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
  • #208224
Closed
Open
Issue created Feb 26, 2020 by Dov Hershkovitch@dhershkovitch🗒Developer

Move cluster health feature into GitLab Core

This is an implementation issue to move our cluster health within the Monitor stage into Core

This should have a seperate MR to update our documentation as well.

we should probably close/verify #219992 (closed) once this issue gets implemented

Technical notes

  • Related to the core version yml config/prometheus/cluster_metrics.yml, @splattael said: We should then move the EE version into the CE and update the code where the EE version was referenced 👍 (#223693 (comment 367479300))
Edited Jun 25, 2020 by Miguel Rincon
Assignee
Assign to
Time tracking