Skip to:
After restarting OpenNMS it happens often that pollers produce false alerts that will be resolved after the next polling cycle.
In this case it is the SNMP poller:
The configuration is here: https://github.com/opennms-config-modules/synology/blob/master/synology-monitors.xml#L1-L8
I can't see any poller thread issues in OpenNMS' JVM metrics and also there is no real issue on the monitored device.
So I guess OpenNMS must be doing something wrong.
I will add other examples in the next time.
Got the next one. Multiple ElasticSearch monitors failed after OpenNMS was restarted.
It's a simple HTTP port monitor.
After restarting OpenNMS it happens often that pollers produce false alerts that will be resolved after the next polling cycle.
In this case it is the SNMP poller:
The configuration is here: https://github.com/opennms-config-modules/synology/blob/master/synology-monitors.xml#L1-L8
I can't see any poller thread issues in OpenNMS' JVM metrics and also there is no real issue on the monitored device.
So I guess OpenNMS must be doing something wrong.
I will add other examples in the next time.
Got the next one. Multiple ElasticSearch monitors failed after OpenNMS was restarted.
It's a simple HTTP port monitor.