Copyright © 2004-2018 The OpenNMS Group, Inc.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts and with no Back-Cover Texts. A copy of the license is available at http://www.gnu.org/copyleft/fdl.html OpenNMS is the creation of numerous people and organizations, operating under the umbrella of the OpenNMS project. The source code is published under the GNU Affero GPL, version 3 or later and is Copyright © 2002-2018 The OpenNMS Group, Inc.
The current corporate sponsor of OpenNMS is The OpenNMS Group, which also owns the OpenNMS trademark.
Please report any omissions or corrections to this document by creating an issue at http://issues.opennms.org.
What’s New in OpenNMS Horizon 23
Java 8: OpenNMS Horizon 23 requires Java 8 as the runtime environment. To run Horizon 23, we recommend the most recent version of Oracle JDK 8 for your platform.
PostgreSQL 9 or higher: Horizon 23 requires Any supported version PostgreSQL 9 or higher. As of this writing, PostgreSQL 9.3 is the earliest version under active support, but OpenNMS is known to work with at least PostgreSQL 9.1 and up.
Vacuumd Alarm Handling
In previous OpenNMS releases, a large portion of the alarm workflow was handled by Vacuumd automations, triggers, and actions. As part of the work to implement alarm correlation, this logic has been moved to Drools, running inside Alarmd.
If you made any changes to
vacuumd-configuration.xml related to alarms, it is strongly recommended you port them to the new Alarmd Drools context.
The Drools rules are in the
Also, we no longer generate
Instead, it is recommended that you add Drools rules to react to alarm changes.
For more complicated integrations, we also have a new API —
AlarmLifecycleListener — for reacting to alarm changes.
OpenNMS Correlation Engine ("Sextant") Proof of Concept
Horizon 23 introduces the groundwork for supporting correlation of alarms into meta-alarms called "situations" using an external engine called the OpenNMS Correlation Engine. Situations are OpenNMS alarms that contain one or more triggering alarms, which allows them to be browsed, acknowledged, and unacknowledged just like any other alarm. A high-level overview of the goal and implementation of correlation can be seen on the Sextant wiki page.
Please note that implementing OCE is an advanced topic and there is still work to do before it is ready for general use. While the OpenNMS core supports situations, the logic of creating them is part of the OCE, which is designed to run in a separate Karaf container. Full support for OCE and correlation is due to be released in Horizon 24.
In addition to the Alarmd Drools updates mentioned previously, there have been some other enhancements made to Alarmd.
Traditionally, OpenNMS has created and resolved alarms in pairs, with one alarm representing the triggering event (or events), and then a second alarm representing the resolution. Horizon 23 changes this default behavior to use a single alarm to track the problem state, incrementing the alarm count when it occurs while in a problem state, or when moving from resolved back into a problem state. Additionally, you can configure OpenNMS to create a new alarm if a problem happens again.
These behaviors are controlled by the introduction of 2 new settings in the
This setting reverts to the old (pre-23) behavior of creating separate alarms for a problem and its resolution.
This setting forces Alarmd to create a new alarm if a problem reoccurs, rather than incrementing an existing alarm. (Note: this is ignored if
legacyAlarmStateis set to
These improvements are covered in a lunch and learn video we published recently, if you would like to learn more.
Kafka Data Collection Sync
In addition to publishing events, alarms, and node inventory to Kafka, we can now publish collected time-series data to the Kafka bus as well.
In addition to the Minion, we have added a new container-based subsystem called "Sentinel." The Sentinel is a standalone container that can be configured to run a subset of OpenNMS daemons as a standalone tool, to aid in horizontal scaling and/or high availability.
This initial release of Sentinel is designed to run our Karaf/Camel/SQS-based messaging bus, syslog listener, Netflow receiver, and Newts and Elasticsearch persistence.
A number of monitors now support using placeholders in parameter values to allow runtime substitution of IP address, node ID, and so on. (See: NMS-10200)
A new WSMan monitor has been added which can use WQL filters against an endpoint to detect arbitrary services.
The web UI now fully supports configuring date formats and user time zone in
opennms.propertieswhich was partially introduced in Horizon 22.
Daemon reloading can now be done from the Karaf shell. Also, Syslogd and Trapd can now respond to daemon reload events.
The RadixTreeSyslogParser now handles Cisco Syslog Message formats.
RPC to Minions is now fully supported when using Kafka rather than JMS.
A bunch of tools for checking the health of OpenNMS, Minions, and Sentinel containers have been added to the Karaf command-line. (Run
health:check --helpfor more details.)
Many other improvements were made to the flow support introduced in Horizon 22.
A number of VMware improvements have been made including configurable timeouts and hanlding of unacknowledged vSphere alarms.
Many subsystems have been improved as part of the refactoring to make them capable of running in the Sentinel container.
The OSGi Plugin Manager has been updated to version 1.1.0.
A policy (
ScriptPolicy) has been added to Provisiond that allows you to run arbitrary Groovy scripts before persistence. An example policy can be found in
Release 24.0.0 is the latest stable release of OpenNMS. It contains a large number of bug fixes and enhancements, most notably adding support for real-time telemetry flow processing. For a high-level overview of what’s changed in OpenNMS 24, see What’s New in OpenNMS 24.
The codename for 24.0.0 is TODO NOT DEFINED YET.
The NCS-Alarm page and the NCS-Topology-Plugin have been removed. See issue TODO MVR.