Skip to Content
This is the latest documentation for BMC Helix Network Management (formerly known as Netreo).

 

Add a Threshold Check to a Device Template

Statistic Pairs

In Netreo, many collected statistics are configured and monitored as pairs (for example, bandwidth utilization pairs inbound traffic with outbound traffic). Threshold checks are also configured in these same pairs, with the opposing statistics identified as VARIABLE ONE and VARIABLE TWO in the check (the actual statistic name is also identified alongside the variable label). The static threshold and anomaly detection settings for each variable are independent, but all other configuration settings for the check are shared between the two.

When configuring static threshold values, the units for the high and low fields will automatically be appropriate for the type of statistic selected (e.g. CPU utilization would show percent, while latency would show seconds). A pull-down selector next to the value allows you to specify a multiplier prefix for the entered value. This allows you to configure the check using values with which you are comfortable and have Netreo do the math for you.

Errors Per Second

Netreo always measures errors per second values as milli-errors per second. This allows for err/sec measurements of less than one. See Understanding Errors per Second for more information on calculating err/sec values that can be used in threshold checks. When entering err/sec values remember to select the milli (m) multiplier prefix.

Add a Threshold Check

To add a threshold check to a device template follow the steps below. (See Threshold Check for configuration best practices.)

  1. Log in to Netreo as a user with the SuperAdmin access level.
  2. Go to the main menu and select Administration > Templates to open the Device Templates Administration page.
  3. Locate the device template to which you would like to add a threshold check and select its edit icon in the ACTIONS column.
  4. In the Template Components panel locate the Thresholds table.
  5. Select the add threshold check button (+symbol).
    1. In the GROUPING OPTION field select the general group type of the statistic that you would like to monitor.
    2. In the SELECT A THRESHOLD field select the specific statistic that you would like to monitor.
    3. Select Select Threshold.
  6. If you wish to add the threshold check to the device template, but do not want it to be active yet, select the Enable/Disable switch to disable the check. (Select again to re-enable the check.)
    • The threshold check is added to all applicable devices, but set to disabled.
  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 additional alert notifications 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) disables 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 ACTION GROUP field as well as to the groups in the ESCALATION 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 CATEGORY field select the grouping that has the greatest relevance to the statistic. 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 to which the template is applied.
  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 should be sampled for the calculated average.
      • See below for best practices regarding static threshold timing.
  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/Edit Thresholds.
  16. Now follow the instructions in Re-Apply Device Templates After Editing.

Modify a Threshold Check

Once added to a device template, you may:

  • edit the check
  • delete the check

by selecting the appropriate icon in it's ACTIONS column.

Deleting a Threshold Check From a Device Template

Deleting a threshold check from a device template does not remove the threshold check from any devices to which it was previously added by that template. Once added to a device, a threshold check may not be removed, it may only be disabled.

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC Helix Network Management