Skip to:

Skip to Jira Navigation
Skip to Side Navigation
Skip to Main Content

Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)

OpenNMS

Software project

Menu

You're in a company-managed project

es-rest: Non-persisted events overwrite single ES document with id=0

Description

If you set the es-rest forwarder to 'forwardAllEvents', events that are not persisted to the database are stored in the same, single ES document with the 'id' of zero. Subsequent events overwrite the document with a new version of the same document instead of generating additional documents.

We need to change the forwarder so that even if incoming events do not have database IDs, they generate separate ES documents.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Jesse White January 27, 2017 at 10:30 AM

PR: https://github.com/OpenNMS/opennms/pull/1253

Fixed in https://github.com/OpenNMS/opennms/blob/fd688288f8c0340f49c16e2c9f670c2adb718463/features/opennms-es-rest/main-module/src/main/java/org/opennms/plugins/elasticsearch/rest/EventToIndex.java#L538

Seth Leger January 25, 2017 at 8:21 AM

This needs to be tested on various versions of Elasticsearch because the behavior seems to be different on 1.7 and 2.4.

Fixed

Details

PagerDuty

Created January 20, 2017 at 6:21 PM

Updated January 27, 2017 at 3:22 PM

Resolved January 27, 2017 at 10:31 AM