Hey guys,

the remote poller does not honor the downtime model when communication back to the central master opennms instance. In case of an outage the remote poller correctly switches the polling interval as configured in the poller-configuration.xml, however it does not change the communication interval to the master instance.
This leads to the funny effect, that an outage is reported to the central master and theoretically resolved a couple of seconds later, but due to the static reporting schedule escalated down the destination path.
It would be wise to either adapt the reporting interval or report exceptionally to the master instance on status change.

Thanks,