What’s New in OpenNMS Horizon 36

The contents of etc/datacollection-config.xml and etc/datacollection/*.xml are migrated into the database during the upgrade process, and the original files are moved to etc_archive/. After upgrade, manage SNMP data collection through the *Administration → Manage SNMP Data Collection Config* page (or the REST API under /api/v2/datacollectionconf). Direct edits to the archived XML files no longer take effect.

The contents of snmp-config.xml are migrated into the database during the upgrade process, and the original file is moved to etc_archive/.

After upgrade, manage SNMP configuration through the Integrations → SNMP Agent Configuration page (or the REST v2 API under /api/v2/snmp-config). Direct edits to the archived XML file no longer take effect.

The new UI supports definition lookup by IP address and location, profile management, and supports both IPv4 and IPv6.

The legacy file-based SNMP credential encryption feature (the org.opennms.snmp.encryption.enabled property and the snmp-config-encrypt / snmp-config-decrypt Karaf commands) has been removed. The upgrade handles existing encrypted configurations automatically. For protecting SNMP credentials, use Secure Credentials Vault (SCV) metadata expressions in your SNMP configuration.

See SNMP Configuration REST API for details.

The contents of trapd-configuration.xml are migrated into the database during the upgrade process, and the original file is moved to etc_archive/.

After upgrade, manage trapd configuration through the Integrations → Trap Configuration page (or the REST v2 API under /api/v2/trapd). Direct edits to the archived XML file no longer take effect.

See Trapd REST API (v2) for details.

Individual services in service-configuration.xml can now be enabled or disabled at runtime via environment variables, using the pattern CORE_SERVICE_<NAME>_ENABLED. For example, set CORE_SERVICE_TELEMETRYD_ENABLED=false to disable Telemetryd without editing the configuration file.

This is particularly useful for containerized deployments where service composition is controlled via environment. Existing enabled="true|false" values in the file remain the default when no environment variable is set.

The OSGiBasedTicketerPlugin is now the default ticketer plugin. Ticketing is automatically enabled when an OSGi-based ticketer plugin is installed and disabled when it is removed. The NullTicketerPlugin and the opennms.ticketer.plugin property have been removed.

If you have opennms.ticketer.plugin=org.opennms.netmgt.ticketd.NullTicketerPlugin in a custom properties file under etc/opennms.properties.d/, remove that entry before upgrading. If you previously set opennms.ticketer.plugin=org.opennms.netmgt.ticketd.OSGiBasedTicketerPlugin, that entry is now redundant and can be removed. The opennms.alarmTroubleTicketEnabled property is no longer required but can still be used to explicitly enable or disable ticketing.

The Vue-based web UI now supports a light/dark theme toggle, in addition to the system-default option.

The contents of the file eventconf.xml will be stored in the database during the upgrade process and all files in etc/events will be moved to etc_archive. These events will not be imported into the database.

After upgrade, manage event configurations through the Administration → Manage Event Configurations page (or the REST API under /api/v2/eventconf).

See Migrating event files after upgrade for the steps to re-upload your customized event files from etc_archive/events/.

The WMI monitor, detector and collector had been removed, as the WS-Man integration offers better support for newer versions of the Windows operating system.

The SNMP implementation JoeSNMP was removed in OpenNMS Horizon.

The C3P0 connection pool factory (org.opennms.core.db.C3P0ConnectionFactory) and etc/c3p0.properties have been removed. HikariCP is now the only supported pool, and has been the default since OpenNMS Horizon 35.

If your opennms-datasources.xml explicitly sets factory="org.opennms.core.db.C3P0ConnectionFactory", remove that attribute before upgrading.

OpenNMS Horizon now requires PostgreSQL 14.x or newer. If you are running an older version, you must upgrade to PostgreSQL 14 or later. Attempting a schema upgrade with install -dis will result in an error. If upgrading PostgreSQL to at least version 14 isn’t possible and you’re completely blocked, the -Q flag lets you skip the version check. Use this only as a last resort, since it may affect compatibility. Be aware that doing so takes you beyond supported configurations — here be dragons.