Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-11572 Prevent alarms from being correlated again after being removed from a situation
  3. NMS-11717

Remove feedback submission actions from Opennms so that OCE is the authoritative source of situation changes



    • Type: Sub-task
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 24.0.0
    • Component/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
    • Sprint:
      Horizon - October 24th 2018, Horizon - October 31st 2018, Horizon - November 14th 2018, Horizon - November 21th 2018, Horizon - November 28th 2018, Horizon - December 5th 2018


      Currently Opennms takes action when feedback is submitted. It will remove an alarm from a situation for example. We will change this behaviour so that Opennms does not take action directly on feedback submission besides persisting the feedback and notifying handlers (sending to kafka for now).

      This way we rely on OCE taking action on the feedback and notifying Opennms via a situation record with the changes applied. This will avoid race conditions that may arise due to having two entities taking action on feedback. It also helps to encapsulate all of the situation logic on the OCE.

      In order fo this to work we will need to update how Opennms handles received situations. Currently when the list of alarms are recorded for a situation they are performed additively. In order to remove alarms from situations we will need to treat the OCE situation source as authoritative and record the list as it told us (removing any alarms that are no longer present).




            • Assignee:
              mbrooks Matthew Brooks
              mbrooks Matthew Brooks
            • Votes:
              0 Vote for this issue
              1 Start watching this issue


              • Created: