Hello
We have a number of clients with "Secondary" routers, which when not in use, do not respond to ping due to the way these devices are load balancing.
What we would like to do is have the "Secondary" router in monitoring, but have it constantly paused, and then resume when the primary router stops responding to ping.
Primary Router goes down > Secondary Router resumes based on the status change of the Primary Router.
The best way I would see this to be possible would be a State Change Trigger; so for instance calling the API to "Pause" the Secondary for 1 minute, to in essence, resume the sensor when Router 01 goes down.
Is this possible, and if so, is there a way to do so without specifying the Sensor ID individually per device (i.e /api/pause.htm?id=objectid&pausemsg=yourmessage&action=0, is there a way to get Object ID to auto detect a device with say a certain name or tag convention as opposed to inputing the exact Object ID of the secondary)
Hello Andrew,
thank you for the KB-Post. The approach is a good one, however getting the IDs (to pause other objects) isn't really possible via tags or some such. The API calls need to be configured manually with the objects to pause. If you are using tags (with the secondary devices), an indirect approach may be, that first pulling a list of all sensors with the specified tag, to get their IDs, and then iterate over this list of IDs with API calls to pause / resume them.
best regards.
Aug, 2018 - Permalink