Currently the distributed monitor is not identified as 'disconnected' for 10 minutes after it has last checked in. I have some critical distributed monitors and would like to know if they are not monitoring much sooner than that.
As a workaround I could probably configure a poller to see if the process is running on the remote node, but the fact that the process is running doesn't ensure it's talking to OpenNMS.
I would like to see a configuration parameter to allow for any disconnection timeout.
Environment
Operating System: All
Platform: All
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:
Seth Leger August 19, 2013 at 11:07 AM
I added a opennms.pollerBackend.disconnectedTimeout system property that will allow you to configure this setting inside the opennms.properties file. The default value is 600000 (10 minutes). Like many other system properties, it is used as a replacement token inside the Spring context files. Marking as fixed.
Currently the distributed monitor is not identified as 'disconnected' for 10 minutes after it has last checked in. I have some critical distributed monitors and would like to know if they are not monitoring much sooner than that.
As a workaround I could probably configure a poller to see if the process is running on the remote node, but the fact that the process is running doesn't ensure it's talking to OpenNMS.
I would like to see a configuration parameter to allow for any disconnection timeout.