Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
gwcelery
gwcelery
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 12
    • Merge Requests 12
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • emfollow
  • gwcelerygwcelery
  • Issues
  • #297

Closed
Open
Opened Feb 20, 2020 by Leo Pound Singer@leo-singerOwner

Break GWCelery nagios check into several services

I am guilty of basically ignoring Nagios alerts from GWCelery. The reason is that the GCN connection is flaky and goes up and down several times a day. Since there is only one Nagios service for each GWCelery deployment, the flakiness of that one subsystem dilutes the urgency associated with other services. We should break the GWCelery nagios check into several individual services so that we can set alert notifications on the other, non-flaky components.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: emfollow/gwcelery#297