Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-12143

Share thresholding state across Sentinels

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 25.0.0
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None

      Description

      One of the main challenges in supporting thresholding on Sentinel is sharing the internal thresholding state across the pool of Sentinels. Sentinels may be added or removed anytime, and we need to ensure that state of the thresholds are preserved.

      Here is an example scenario to consider:

      1. Sentinel A processes a CollectionSet with a relative-change threshold associated, the current value is 5
      2. Sentinel A dies
      3. Sentinel B processes the following CollectionSet for that same threshold with a value of 999, we expect the threshold to be triggered

        Attachments

          Activity

            People

            • Assignee:
              mbrooks Matthew Brooks
              Reporter:
              j-white Jesse White
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: