This Week in OpenNMS: April 23rd, 2018

It's time for This Week in OpenNMS!

In the last week we released Horizon 21.1.0, Meridian 2016.1.12, and Meridian 2017.1.7, and did more work on Drift and preparing for Meridian 2018.

Github Project Updates

  • Internals, APIs, and Documentation

    • Markus worked on some Elasticsearch updates.
    • I worked on refactoring out our Karaf container build so it can be shared between Minion and Sentinel.
    • Chandra worked on making telemetry persistence groovy scripts reloadable at runtime.
    • Patrick did performance improvements to flow query indexing.
    • Markus added support for handling source and destination in classification rules.
    • Jesse fixed a thread-safety issue in the index strategy code.
    • Jesse worked on improving startup cache handling in Newts.
    • Antonio worked on some bridge discovery bugs in Enlinkd.
    • Ronny worked on refactoring a number of MIB definitions.
  • Web & UI

    • Markus made some enhancements to the classification web UI.
    • Christian made it possible to use an embedded grafana box in the web UI when running behind a proxy.
    • David did some work on a correlation proof-of-concept in OpenNMS.js and Helm.

OpenNMS Horizon 21.1.0 Released

OpenNMS Horizon 21.1.0 (code name: Replicant) was released last Thursday.

It contains bug fixes and a few enhancements, including support for forwarding events, alarms, and nodes to Kafka.

For more details on what has changed, see the complete change log.

OpenNMS Meridian 2016.1.12 and 2017.1.7 Released

Both releases include a small bug fix in event handling.

Additionally, Meridian 2017.1.7 contains a few other small bug fixes, enhancements, and configuration updates. See the release announcement for more details.

In Development: Sentinel

As we wrap up the Drift project (expected to be included in OpenNMS Horizon 22), we are starting up a new project codenamed "Sentinel" to create a new Karaf container capable of running some components of OpenNMS standalone.

In the short term, the goal of Sentinel is to be able to horizontally scale Drift, receiving telemetry data and enhancing it with additional OpenNMS metadata, then passing it on to Elasticsearch for storage and indexing.

Over time, we should be able to expand it out to run other components of OpenNMS as well, eventually being able to run any combination of OpenNMS subsystems across multiple systems and/or processes.

Upcoming Events and Appearances

Until Next Week…

If there’s anything you’d like me to talk about in a future TWiO, or you just have a comment or criticism you’d like to share, don’t hesitate to say hi.

- Ben

Resolved Issues Since Last TWiO

  • HELM-90: Options tab in Alarm Table shows OpenNMS homepage
  • HZN-1256: Kafka Entity Streams
  • HZN-1272: EventToIndex - Alarm Change Old/New parameters submitted to ES as single string and not JSON objects
  • HZN-1281: Netflow - Limit queries to specified indices
  • HZN-1296: Flow documents logged against incorrect ES index
  • HZN-1298: Make time padding for IndexSelector configurable
  • NMS-8974: missing files in debian x64 distribution
  • NMS-9559: Store forwarders lacks of memory
  • NMS-9831: Karaf opennms-es-rest Plugin - Creating OID mappings causing ES index mappings to exceed 1000
  • NMS-9915: JasperStudio extension dependency error
  • NMS-9916: The Grafana Box on the front page doesn't work when Grafana is behind a Web Proxy
  • NMS-9937: Refactor UserGroupLdapAuthoritiesPopulator to provide a default role.
  • NMS-9952: The JDBC Collector doesn't work

Previous Post Next Post