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 44,287
    • Issues 44,287
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,282
    • Merge requests 1,282
  • 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.orgGitLab.org
  • GitLabGitLab
  • Issues
  • #255304
Closed
Open
Issue created Sep 24, 2020 by Vitali Tatarintev@ck3g🔴Maintainer

Figure out the need of `prometheus_computed_alerts` feature flag

There is a prometheus_computed_alerts feature flag in the codebase introduced in the following MR !13443 (merged)

It doesn't seem to be used.

Screenshot_2020-09-24_at_11.07.48

Screenshot_2020-09-24_at_11.08.12

In that case, that looks like a dead code.

We need to figure out whether we need that feature and move forward and roll it out or remove the dead code.

Assignee
Assign to
Time tracking