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

Allow notifd auto-ack to use reduction-key

    XMLWordPrintable

    Details

    • Type: Enhancement
    • Status: Resolved (View Workflow)
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: 1.12.1
    • Fix Version/s: None
    • Security Level: Default (Default Security Scheme)
    • Labels:
      None
    • Environment:
      Linux

      Description

      Problem description:

      The auto-acknowledge can only perform matching against the nodeid, service, and interface of a notification. This is not useful for events that use a more sophisticated reduction key. For example, SNMP_Link_Down traps reduce using the interface index, which is %param1% in the trap's varbind payload. The auto-acknowledge sees Link_Down traps for a source as having the same source nodeid and interface, even if the index differs, and will auto-ack incorrect notifications.

      For example, given the following three events/notifications:

      • Receive SNMP_Link_Down trap for index 1 from node A
      • Receive SNMP_Link_Down trap for index 2 from node A
      • Receive SNMP_Link_Up trap for index 1 from node A
        The auto-ack will send a RESOLVED notification for the "SNMP_Link_Down trap for index 2 from node A" notification.

      Enhancement request:
      Add the ability for the <match> in auto-acknoledgement definitions to use the event's reduction key in the exact same way that the Alarms interface does, so that RESOLVED notifications that depend on sophisticated reduction-keys will be raised correctly.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                agalue Alejandro Galue
                Reporter:
                caneylan Christopher Neylan
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: