Skip to:

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

The Elasticsearch ReST Plugin documentation is not clear about how to forwards alarms

Description

On the administration docs, the ES ReST Plugin says it will create indices for RAW events, alarms, and alarm change events:

http://docs.opennms.org/opennms/releases/20.1.0/guide-admin/guide-admin.html#_elasticsearch_rest_plugin

Also says, those features are enabled by default.

But, on a VM running 19.1.0, and another VM running 20.1.0, and another VM running Meridian 2017.1.0, all configured to forward events to an Elasticsearch instance running 5.5 (and then to another different one running 5.6.3), only the index for events is created and updated.

No indices are created or updated for alarms or alarm changes, even knowing that I've generated alarms (by stopping monitored nodes, and then restoring those nodes).

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Jesse White July 31, 2019 at 5:23 PM

Alarm change notifier is gone and has been replaced with the "alarm history" feature which is documented here: http://docs.opennms.org/opennms/releases/24.1.2/guide-admin/guide-admin.html#ga-alarm-history

Alejandro Galue January 4, 2018 at 7:44 PM

As an FYI, the alarm-change-notifier feature is broken in 21.0.2, you cannot install it in Karaf anymore, maybe this fact deserves a new JIRA issue.

Alejandro Galue November 28, 2017 at 1:28 PM

I agree with "As long as the documentation is consistent, it might not be that crucial". That being said, and considering that the documentation itself is confusing and doesn't mention alarms, I'll let you decide what to do. At least I know the workaround even if explaining that to a customer could confuse them even more.

Markus von Rüden November 28, 2017 at 1:11 PM

It would be nice if the feature name would reflect the actual meaning of what is going on, but I also don't think it is that crucial. For example, the documentation could always talk about the Alarm Notifier and only the installation part mentions a feature called alarm-change-notifier. As long as the documentation is consistent, it might not be that crucial.

Jesse White November 27, 2017 at 8:27 PM

I agree with the points above expect for the first. Personally, I don't see the value in changing the name of the feature from alarm-change-notifier to alarm-notifier. Does the word 'change' really change that much here?

Won't Fix

Details

Assignee

Reporter

Labels

Components

Sprint

Affects versions

Priority

Parent

PagerDuty

Created October 17, 2017 at 6:28 PM
Updated April 1, 2020 at 1:36 PM
Resolved July 31, 2019 at 5:23 PM