Set custom Connectivity status thresholds
By design, the Xprotect agents send heartbeats to the Xprotect tenant once every Five minutes. If Xprotect does not receive Six consecutive heartbeats (that is, no heartbeat for the last 30 minutes), it considers that the host is Offline. If Xprotect does not receive heartbeats for 14 consecutive days, Xprotect considers that the host is Unreachable.
The data displayed on the Dashboard widgets, the status of the hosts on the Hosts page, and the filters and Bookmarks that use Connectivity status as a criteria use these default thresholds.
Custom Connectivity status thresholds
You can change the default Connectivity status thresholds to more suitable values for your instance and usage. For example, if you plan to enable the Auto-Delete Unreachable Hosts feature to clean up scaled-down cloud-based hosts from the Hosts page. Setting the Unreachable threshold to a value that is close to the Offline threshold will delete entries of Unreachable hosts quickly. This reduces clutter on the Hosts page.
The minimum allowed value for the Offline threshold is Eight minutes, and the maximum allowed value is one hour. The Unreachable threshold must always be above the Offline threshold, and the maximum allowed value is 30 days.
If you set custom Connectivity status thresholds, the data displayed on the Dashboard widgets, the status of the hosts on the Hosts page, and the filters and Bookmarks that use Connectivity status as a criterion, use the custom thresholds.
Set custom thresholds
Decide upon the values of the thresholds that you want to set.
|
Next steps
-
If you are setting custom Connectivity status thresholds with the intention of using the Auto-Delete Unreachable Hosts feature, see Schedule auto-deletion of unessential Unreachable hosts for more details.