As you can see in the screenshot, the monitor class is N/A after reloading the poller config. In this case the poller won't work. I have to restart ONMS to get the poller working.
If you define new services in poller-configuration.xml a service restart of OpenNMS is necessary.
So I guess my described behaviour is correct. Reloading changes in an existing poller is possible, but not new ones.
fooker April 11, 2019 at 8:17 AM
There is a note about that behavior in opennms-doc/guide-admin/src/asciidoc/text/service-assurance/configuration.adoc which should be removed if fixed.
Marcel Fuhrmann March 8, 2017 at 5:12 PM
Same with Asterisk monitor. I've added the service on the interface and reloaded pollerd. Not sure if the poller works in this state... Maybe I can figure it out in a few days.
I've created a http poller and reloaded the pollerd with:
/usr/share/opennms/bin/send-event.pl uei.opennms.org/internal/reloadDaemonConfig --parm 'daemonName Pollerd'
As you can see in the screenshot, the monitor class is N/A after reloading the poller config.
In this case the poller won't work. I have to restart ONMS to get the poller working.
I've tested this with JDBC query monitor too.