Uploaded image for project: 'Architecture for Learning Enabled Correlation (ALEC)'
  1. Architecture for Learning Enabled Correlation (ALEC)
  2. ALEC-15

Handling of duplicate inventory objects in the OpenNMS datasource

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Blocker
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.0.0
    • Labels:

      Description

      Using the OpenNMS Kafka datasource, it is currently possible for 1+ alarms and a node to contribute the same InventoryObject via the InventoryDatasource to the handlers.

      The current implementation of the clustering engine (currently the primary correlator) handles duplicates by ignoring subsequent adds for the same objects. However, the object is removed from the graph on the first delete.

      This means that if alarm A1, and alarm A2 and node N1 all contribute the same object, A1 gets cleared and the InventoryObject derived from A1 is expired, then the object will be removed from the graph.

      The logic should be updated, such that the inventory object is not removed until it is expired from all the providers.

        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: