Add a Threshold Check to a Device

Add a Threshold Check

To add a threshold check directly to a managed device, complete the following steps. (See Threshold Check for configuration best practices.)

(Note: When a threshold check is added to a device, it cannot be removed. It can only be disabled.)

See also, Add a Threshold Check to a Device Template.

1. Log in to Netreo as a user with the Admin access level or higher.
2. Locate the device to which you would like to add a threshold check and select it to open its device dashboard.
   • Specific devices can be located in Netreo by either drilling in to a Tactical Overview dashboard widget or searching for the device by name using the search feature at the top of the main menu.
3. Select the gear icon in the top right of the dashboard to open the dashboard administrative view.
4. Select the Instances tab.
5. Locate the panel for the statistic type containing the statistic you would like to monitor and select it to open the panel.
   • If the statistic you would like to monitor is in the Network panel, use the pull-down menu at the top right and select Thresholds to display the network interfaces.
6. Locate the specific statistic to which you would like to add a threshold check and select its add threshold icon (+) in the ACTIONS column.
7. In the ACTION GROUP field select the action group(s) to receive alert notifications  before escalation.
8. In the ESCALATION GROUP field select the action group(s) to receive alert notifications after escalation.
9. In the RENOTIFICATION INTERVAL field enter the number of minutes for Netreo to wait before sending another alert notification if the problem is not acknowledged by a user.
   • Alert notifications are sent to the action groups in the ACTION GROUP field.
   • The default value of 1440 minutes (24 hours) is recommended to minimize alert noise.
   • Setting a value of 0 (zero) will disable renotifications.
10. In the ESCALATE AT field enter the number of alert notifications after the first for Netreo to wait before sending alert notifications to the action groups in the ESCALATION GROUP field, as well as to the groups in the ACTION GROUP field.
    • The default value of 1 means that a total of 2 alerts must be sent before escalation groups start receiving them.
11. In the STATISTICAL GROUP field select the type that has the greatest relevance to the check. This field determines which statistical calculations this check contributes to for reports.
12. (Optional) In the SUBSTRING field, enter a string or regular expression to include or exclude specific interfaces from this check using a match to the interface name/description.
    • If this field is left empty, the device template attempts to add the configured threshold check to every interface of every device it is applied to.
13. If you would like to configure static threshold  monitoring (repeat these steps for each variable if two variables are present):
    1. (Optional) In the HIGH warning field (yellow) enter the exact value at which the check should enter the WARNING state for high values.
       • Next to the value type, select the multiplier prefix.
    2. (Optional) In the HIGH critical field (red) enter the exact value at which the check should enter the CRITICAL state for high values.
       • Next to the value type, select the multiplier prefix.
    3. (Optional) In the LOW warning field (yellow) enter the exact value at which the check should enter the WARNING state for low values.
       • Next to the value type, select the multiplier prefix.
    4. (Optional) In the LOW critical field (red) enter the exact value at which the check should enter the CRITICAL state for low values.
       • Next to the value type, select the multiplier prefix.
    5. In the TIME PERIOD field select the time period over which data values will be sampled for the calculated average.
       • See Best Practices below for best practices regarding threshold check time periods.
14. If you would like to configure anomaly detection(repeat these steps for each variable if two variables are present):
    1. In the Boundary field select whether to check for upper boundary anomalies, lower boundary anomalies or both.
    2. In the Sensitivity warning field (yellow) select the desired sensitivity. (This should always be at least one setting higher than the critical sensitivity field, so that the warning state occurs first.)
    3. In the Sensitivity critical field (red) select the desired sensitivity. (This should always be at least one setting lower than the warning sensitivity field, so that the warning state occurs first.)
    4. In the Season field select the desired season for the data samples.
    5. (Optional) In the Min Value field set the minimum value that a polled value must be to qualify for anomaly detection.
       • The value entered in this field should be specified in the same base unit displayed in the static threshold configuration, without the prefix (for example: bytes, not megabytes; seconds, not milliseconds). Note: For bandwidth monitoring (only), the value must be specified in bits per second, and not as a percentage.
15. Select Create Threshold.

Modify a Threshold Check

Once added to a device, you may:

• Edit the check
• Delete the check

These actions may be performed by selecting the appropriate icon in the check's ACTIONS column.