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

Threshold state keys do not incorporate the collected resource's instance label

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Meridian-2019.1.0, 25.1.0
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Sprint:
      Horizon 2019 - October 2nd, Horizon 2019 - October 9th

      Description

      The key used to persist threshold states does not currently take into account the collected resource's instance label. This leads to key collisions for states where multiple thresholding evaluation states refer to the same persisted state.

      During steady state operation this shouldn't manifest as an issue since the in-memory copy will be used. However upon restart we load state from the persistence store and multiple thresholds will obtain the state that resulted from the collisions which will cause unexpected thresholding behaviour.

        Attachments

          Activity

            People

            • Assignee:
              mbrooks Matthew Brooks
              Reporter:
              mbrooks Matthew Brooks
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: