Configure alert thresholds to suppress alerts

Monitoring the performance of checks is important, but not every check failure is an immediate cause for concern.

For example, for a performance monitoring check, a single failure may not be an issue if a device often performs resource intensive tasks where there may be spikes of high system activity. However, consecutive failures may indicate a sustained bottleneck and require further investigation.

In these cases, you can configure server alert thresholds and workstation alert thresholds to set the number of consecutive check failures before a check alert is generated and sent.

A check failure below the configured alert threshold is reported as a soft failure (yellow tick) and an alert is not sent
If a check continues to fail, and then exceeds the configured alert threshold, it is reported as failed (red exclamation box) and an alert is sent

If you manually run a check and it fails, it contributes to the number of consecutive failures.

You can configure alert thresholds globally across the Client base or for individual devices for the following check types:

Antivirus Update Check
Bandwidth Monitoring Check
Script Check
SNMP Check
Performance Monitoring Check

You can only configure server alert thresholds for Bandwidth Monitoring Checks and Performance Monitoring Checks.

Configure alert thresholds across the client base

On the N-sight RMM Dashboard, go to Settings > Alerts > Alert Policy
Select the Server Alert Thresholds or Workstations Alert Thresholds tab
Use the drop-down menu for the target check type to select the number of consecutive check failures before an alert is generated
Select OK to apply

Configure alert thresholds for an individual device

On the N-sight RMM Dashboard North-pane, right-click the target device and select Edit Server or Edit Workstation
Select Alert Policy
Use the drop-down menu for the target check type to select the number of consecutive check failures before an alert is generated
Select OK to apply