Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
L
lvalert
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 4
    • Merge Requests 4
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • lscsoft
  • lvalert
  • Issues
  • #2

Closed
Open
Opened Aug 01, 2018 by Reed Essick@reed.essick

determine whether we still need to monitor known "silent failure mechanism" with lvalert-heartbeat

During O1/2, we occasionally observed "silent failures" in which listeners would stop receiving alerts but the processes would not fail. This motivated the development of lvalert-heartbeat. Although that did not solve the underlying problem, it at least prevented it from being silent.

Because the underlying software libraries within lvalert have changed, this failure mechanism may no longer be relevant. However, we may want to stand up a few extremely long-lived listeners and monitor them to confirm that is the case.

/cc @alexander-pace @patrick-brady

Edited Aug 01, 2018 by Reed Essick
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: lscsoft/lvalert#2