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.
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.