I have verified that the performance of the es-rest forwarder is comparable to the Camel-based version. Because it is easier to support multiple versions of ES with the es-rest forwarder, I'm going to deprecated this feature instead of upgrading Camel to get ES 2/5/5.1 support.

Users who need to forward events and alarms to Elasticsearch should switch over to using the opennms-es-rest forwarder as soon as possible because support for this feature may be removed in a future version of OpenNMS.

Craig's Elasticsearch REST forwarder that is available in OpenNMS 19 supports ES 1, 2, and 5 since it uses REST instead of the version-dependent transport API to insert events. If we can validate the performance of the REST forwarder, it may supersede the Camel forwarder since it has wider compatibility.

FYI, I don't think we'll be able to upgrade to Camel 2.17+ until we upgrade to Spring 4.1 and ActiveMQ fixes their compatibility issues with Spring 4+ inside Karaf. The camel-jms component in Camel 2.17 has changed its Spring compatiblity to "[4.1,5)" so it won't run with Spring 4.0. :-/

The commit in my previous comment has been tagged for 2.17.0

The ES component in Camel 2.16.2 (which is currently the latest release) uses the ES 1.7.3 library.

It looks like there's no release with 2.x support yet.