-
Type:
Story
-
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:None
-
Sprint:Horizon - October 17th 2018, Horizon - October 24th 2018, Horizon - October 31st 2018, Horizon - November 14th 2018, Horizon - November 21th 2018, Horizon - November 28th 2018, Horizon - December 5th 2018, Horizon - December 12th 2018, Horizon - December 19th 2018, Horizon - January 9th 2019, Horizon - January 30th-2 2019, Horizon - Feb 6th 2019
Leveraging the new org.opennms.netmgt.dao.api.AlarmEntityListener API added in Horizon 23, it should be possible to index and maintain alarm state changes in Elasticsearch without the need to rely on database triggers.
Alarms should be indexed and maintained in such a way that allows users to answer the following questions using only the data stored in Elasticsearch.
1) What is the current state of the alarms in OpenNMS?
2) What was the state of the alarms in OpenNMS at some time t?