In this article, we will describe how Pings and Outages work in UISP and how users can configure those features.
Table of Contents
Devicessection and a right panel will open. Click on the Manage tab, expand the Advanced section, enable the Device specific settings to change the ping address.
In this guide, we will talk in detail about how exactly UISP uses Ping for several different purposes and how Outages are configured.
Firstly let's talk about different PING tests in UISP :
Latency PING: In order to measure a device's latency UISP can instruct that device to send a ping. By default, such ping is targeted to the UISP server, but users can redirect it to anywhere else. When the route is set to a different location and the ping target is unreachable, the device's status will remain "Active" because the Monitoring PING is still going through. The situation will be visibly highlighted in the device's Latency graph (a Latency outage).
Monitoring PING: There is a WebSocket channel opened between a device and UISP and both sides are periodically checking if the connection is healthy. If they cannot see each other for a user-specified amount of time, an outage is created and that device status is changed to "Disconnected".
Ping Address: By default, the value of this setting is the same as the UISP hostname. It is, however, possible to change this address and ping a different target for latency reading. In order to measure the Latency ping to the Internet precisely, we suggest using 'ping.ubnt.com' in this field.
Ping interval (default): This value represents a period of time between Latency ping attempts while a device is running normally.
Ping interval (outage): This value represents a period of time between Latency ping attempts while a device is reporting a Latency outage. The idea is that a user probably wants the ping to be more frequent in case of a Latency outage so that the Latency graph is filled with accurate latency values as soon as possible.
PING for 3rd party device: This ping is actively sent from the UISP console (server) in order to monitor the connection to a third party device. Optionally enable this setting in the device specific settings for a third party device.
This configuration influences how the Monitoring Ping behaves. Each value defines a time interval after which a device is considered to be in an outage state after the Monitoring Ping failed. There are different times according to some situations as described below:
Running device reportable outage: This value represents a time interval after which a device is considered in an outage state if it was running normally before.
Restarting device reportable outage: This value represents a time interval after which a device is considered in an outage state if it was in the process of restarting before.
Upgrading device reportable outage: This value represents a time interval after which a device is considered in an outage state if it was being upgraded before.
E-mail report to include outages over: This value represents a time interval after which UISP sends an actual email alert after the Outage status is activated on a device.