Updates required to configure V3 trap notifications.

[mjsiers]

I have added a trapd-configuration.xml file into the etc-overlay directory but my V3 trap messages are not getting logged. Do I need to also update the default snmp-config.xml file? How can I see what the default values are in the current snmp-config.xml file?

[indigo423]

Related to your "Updates ..." statement in your title, do you have updated the container image? In general there the following considerations related custom configuration:

• If you don't persist the opennms/etc directory and have it stateless, you need to inject all custom configuration using the etc-overlay. This is very hard to achieve, cause can create or modify configurations from the Web UI, e.g. adding SNMP communities, add nodes in requisitions, notifications, destination paths, etc. These type of changes are not reflected in your etc-overlay directory. On container restart they get overwritten! If you drop your container everything is lost unless what you have set in your etc-overlay.
• Persist opennms/etc configuration files in a volume allows you to keep changes from a running system. When you do upgrades it is a little bit trickier, cause you need to migrate the etc content in the volume which is probably trickier to access from your host to do the migration.
• IMHO Using local host mounted directories for opt/opennms-etc-overlay and /opt/opennms/etc this gives you the best flexibility for migration for updates and maintaining complex configurations.

The biggest issue here is the fact OpenNMS behaves like a legacy application. To address this issue would be a refactoring to clearly divide persistence for running configuration and startup / initial configurations.