What’s New in OpenNMS Horizon 31
Java 11: OpenNMS Horizon 31 runs on JDK 11.
PostgreSQL 10 or higher: Horizon 31 requires any supported version of PostgreSQL from 10 up to (and including) 15.
Horizon 31 supports plugins using the OpenNMS Plugin API version 1.0 through 1.2.
Since 1.0, OPA has been improved to include time-series performance enhancements and off-heap support, APIs for flow persistence and poller configuration extensions, and enhanced event and monitored service metadata.
Horizon 31 includes the Cloud Services Connector in its default RPM and DEB install, providing access to OpenNMS Time Series DB – a new hosted cloud service which enables scalable metrics storage without the administrative overhead.
Horizon 31.0.0 is the first new major Horizon release to support writing time-series data to a Cortex instance via the optional OpenNMS Cortex Plugin.
The "UI Preview" that was separate from the main UI in Horizon 30 has been integrated into the main web UI where appropriate for Horizon 31.
Network topology discovery ("Enlinkd") has received significant refactoring to make it smarter and more performant.
The work done in Horizon 30, cleaning up and standardizing how our container images are built, has been expanded in Horizon 31. All images (Horizon, Minion, and Sentinel) use the same core, and are now available in amd64, arm64, and arm7 varieties.
Horizon 30 was incompatible with OpenShift, and we have addressed these issues. If you see any weird permissions or ownership problems in an OpenShift environment, log an issue report in Jira.
configurations have been added for thresholding on Collectd and Pollerd threads
The DCB feature has had a number of improvements, including debugging and script enhancements.
The REST API endpoint for configuring external requisitions (aka `requisition-def`s) has been improved to enable targeted updates rather than requiring whole posting of a new configuration.