Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

The Alarm History feature is not working

Description

The alarm history feature, used to forward alarm changes to Elasticsearch is not working on Horizon 26.1.0, but it works on 25.x (verified with 25.2.1).

I'm including a simple test environment with Docker that someone can use to verify that it works with H25 but not with H26.

With H26, there is an exception on karaf.log on every attempt to send an alarm to Elastic:

Interestingly, with Horizon 26.0.0, the alarm history feature works as expected, meaning something changed recently broke it.

Acceptance / Success Criteria

None

Attachments

2

Lucidchart Diagrams

Activity

Chandra Gorantla May 19, 2020 at 2:12 PM

Alejandro Galue May 15, 2020 at 9:41 PM

I've been told that Fedora 32 has some fans, and Docker doesn't run on that version. So, I've included a .tar.gz with a test lab that uses Vagrant/Ansible to set up a VM with Fedora 32 and OpenJDK 11, Elasticsearch 7.6.1, PostgreSQL 12 and OpenNMS with the Alarms History plugin installed.

Only VirtualBox and Vagrant are required to be installed on your machine.

Chandra Gorantla May 15, 2020 at 8:54 PM

Looks like the issue is reproducible only when indexPrefix is set

Ronny Trommer May 15, 2020 at 8:16 PM

I couldn't verify this, I see Alarms coming into my ElasticSearch. This is the content of my org.opennms.features.alarms.history.elastic.cfg:

I just a few gigs in there and no replication and I use the image: opennms/horizon:26.1.0 image.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created May 15, 2020 at 5:42 PM
Updated May 19, 2020 at 4:05 PM
Resolved May 19, 2020 at 4:05 PM
Loading...