Skip to:
It possible to trigger alarms and create a new situation using:
./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'node n6' \ -x 6 ./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'node n7' \ -x 7 ./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \ -p 'related-reductionKey2 uei.opennms.org/alarms/trigger:n6::' \ -p 'node situation-n6-n7'
The related reduction keys on the event are supposed to be authoritative, meaning that if I subsequently send:
./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \ -p 'node situation-n6-n7'
Then the alarm with reduction key 'uei.opennms.org/alarms/trigger:n6::' should be removed from the situation.
This functionality is no longer working, and the alarm remains in the situation.
Fixed in release-24.0.0 with https://github.com/OpenNMS/opennms/commit/26a0b008c4cb5c4a5b3f3654fe29b85ab2f9acf5
release-24.0.0
It possible to trigger alarms and create a new situation using:
./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'node n6' \ -x 6 ./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'node n7' \ -x 7 ./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \ -p 'related-reductionKey2 uei.opennms.org/alarms/trigger:n6::' \ -p 'node situation-n6-n7'
The related reduction keys on the event are supposed to be authoritative, meaning that if I subsequently send:
./bin/send-event.pl uei.opennms.org/alarms/trigger \ -p 'related-reductionKey1 uei.opennms.org/alarms/trigger:n7::' \ -p 'node situation-n6-n7'
Then the alarm with reduction key 'uei.opennms.org/alarms/trigger:n6::' should be removed from the situation.
This functionality is no longer working, and the alarm remains in the situation.