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,814
    • Issues 43,814
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1,446
    • Merge requests 1,446
  • 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
  • #42640
Closed
Open
Created Dec 12, 2019 by Dov Hershkovitch@dhershkovitch👀Developer

Alerting available in Core

Purpose

Gitlab's Holiday gift to the community was to move the Three Pillars of Observability to Core. This includes Metrics, Logging, and Tracing as well as Alerting The link to the blog post can be found here. At a high level, we chose to do beause:

  • It is part of our Stewardship model
  • Observability belongs in Core
  • We want your feedback on Monitoring

This is an implementation issue to move Alerting to Core.

Deliverable

Alerting functionality will be available for all pricing tiers once released.

Implementation details

The linked (sub)issues can be implemented in the following order:

The generic alerts endpoint

  1. Move PrometheusMetric class from EE to CE #199995 (closed)
  2. Move NotificationPayloadParser from EE to CE #200007 (closed)
  3. Move User.alert_bot from EE to CE #200006 (closed)
  4. Move PrometheusAlert from EE to CE #199997 (closed)
  5. Move Alert class from EE to CE #200005 (closed)
  6. Move ProcessAlertWorker and CreateIssueService from EE to CE #200008 (closed)
  7. Move /alerts/notify.json endpoint from EE to CE #200010 (closed)
  8. Move ErrorTracking->Incidents from EE to CE #200011 (closed)
  9. Move Alerts service page from EE to CE #200012 (closed)

Prometheus-specific alerts

  1. Move #auto_resolve_prometheus_alert methods from EE to CE #210524 (closed)
  2. Move Issue.order_created_at_desc scope from EE to CE #210526 (closed)
  3. Move NotificationService#prometheus_alerts_fired and its dependencies from EE to CE #210527 (closed)
  4. Move ProjectAlertingSettings from EE to CE #210529 (closed)
  5. Move Application::Prometheus#alert_manager_token from CE to EE #210530 (closed)
  6. Move Alert services from EE to CE #210534 (closed)
  7. Move PrometheusAlertSerializer from EE to CE #210535 (closed)
  8. Move GitlabAlertEmbedService from EE to CE #210536 (closed)
  9. Move Prometheus-Cluster classes from EE to CE #210539 (closed)
  10. Move read_prometheus_alerts policy from EE to CE #210540 (closed)
  11. Move OperationsController#reset_alerting_token from EE to CE #210541 (closed)
  12. Move CreateEventService and ProcessPrometheusAlertWorker from EE to CE #210531 (closed)
  13. Move Alert::NotifyService from EE to CE #210532 (closed)
  14. Move AlertsController from EE to CE #210537 (closed)
  15. Move Prometheus alerts from EE to CE #210542 (closed)

Issues 1-11 have no blockers and can be implemented in any order.

Edited Apr 16, 2020 by Sarah Waldner
Assignee
Assign to
Time tracking