Skip to:

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

Elasticsearch event forwarding gets Hibernate lazy init exception

Description

I'm seeing a high failure rate on the Elasticsearch event forwarder (around 65%) and it looks like it's due to this exception inside karaf.log. Since it's a Hibernate exception during logging, I'm somewhat confused why the failure rate isn't 100%...

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger May 9, 2017 at 12:41 PM

This feature has been removed, marking as fixed.

commit 7e26bbb3a65cc859dfd0bfb4a3d993a68024a7fa

Seth Leger January 25, 2017 at 10:57 AM

Reducing priority since this forwarder is largely superseded by the es-rest forwarder.

Seth Leger December 6, 2016 at 9:30 PM

The is Umberto's ES forwarder that links in as an EventListener and AlarmNorthbounder.

David Hustace December 6, 2016 at 3:10 PM

Hey, Seth. Which forwarder is this?

Seth Leger December 6, 2016 at 11:11 AM

Based on counters, it looks like all of the messages from the alarmsFromOpennms route have this problem, I think that the events are being processed normally.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created December 6, 2016 at 10:41 AM
Updated May 9, 2017 at 12:41 PM
Resolved May 9, 2017 at 12:41 PM