What’s New in OpenNMS Horizon 35

Event definitions are now stored in the database, enabling dynamic management without requiring eventd restarts. Core OpenNMS events are pre-loaded automatically. Vendor-specific event files are available in ${OPENNMS_HOME}/etc/examples/events/ and can be uploaded through the UI or REST API as needed.

See Event Configuration for details.

The opennms-datasources.xml configuration file has been simplified by making the factory and class-name attributes optional with sensible defaults. The factory attribute now defaults to org.opennms.core.db.HikariCPConnectionFactory and the class-name attribute defaults to org.postgresql.Driver. Existing configurations with these attributes explicitly set will continue to work unchanged. New installations and users updating their configurations can omit these attributes for cleaner, more maintainable configuration files.

The service-configuration.xml configuration file has been simplified by moving service implementation details (class names, attributes, and invoke methods) to defaults in the classpath. Users now only need to specify the service name and enabled status. A complete reference configuration is available in etc/examples/service-configuration.xml.default. Existing configurations continue to work unchanged.

The TestLoadLibraries service has been removed as a separate service entry in service-configuration.xml. Its functionality (testing ICMP and localhost resolution) is now executed automatically as part of the Manager service initialization. This simplifies the service configuration and reduces the number of service entries that must be managed.

OpenConfig telemetry streaming is now supported on Minion. See Set up OpenConfig on Minion for configuration details.

With this release, we’re streamlining the installation process for OpenNMS on both Debian and RPM-based systems by standardizing the installation location to /opt/opennms. This update provides a consistent deployment path, simplifies future upgrades, and minimizes conflicts caused by differing directories.

Before upgrading, we strongly recommend backing up your existing installation including configuration files, databases, and any custom scripts or integrations to prevent data loss or disruption.

JRobin, the pure-Java RRD implementation has been removed. The class org.opennms.netmgt.rrd.jrobin.JRobinRrdStrategy is no longer available. The Utilities to convert and analyze JRobin files (.jrb) are still available and usable.