Configuring Alarm Thresholds

This article explains how to configure probes to compute baselines, publish QoS to the message bus, and publish threshold alarms, using Admin Console.
uimpga-ga
This article explains how to configure probes to compute baselines, publish QoS to the message bus, and publish threshold alarms, using Admin Console.
Contents
Certain probes support the configuration of baselines and thresholds in CA Unified Infrastructure Management 9.0.2 and later using MCS. For more information, see Configuring Alarm Thresholds in MCS.
Configuring Baselines
The baseline_engine probe calculates a baseline for all monitoring QoS metrics that have
Compute Baseline
enabled in the
CA Unified Infrastructure Management Probes
domain that it belongs to. To provide a statistically accurate baseline while minimizing system resource use, baseline_engine uses a four-step process.
  1. The probe listens for messages with the subject QoS on the message bus.
  2. The probe calculates an initial baseline data point for each QoS monitor that has
    Compute Baseline
    enabled.
  3. The probe then collects the data it uses to calculate an overall baseline for a QoS monitor during the same one-hour interval each week for 4-12 weeks. (You choose the retention period, from a minimum of 3 weeks to a maximum of 12 weeks.)
  4. The probe sends the data points to the qos_processor, which processes the data and writes it to the
    CA Unified Infrastructure Management
    database.
Publishing QoS Data
To send the desired QoS data to the bus, select one or more of the following actions:
  • Publish Alarms
    - Allows the probe, or the baseline_engine or prediction_engine (on behalf of the probe), to generate dynamic, static, and predictive alarms.
    These alarms appear on CA Unified Service Manager or Infrastructure Manager.
  • Publish Data
    - Publishes QoS data from monitoring probes to the UIM message bus.
  • Compute Baseline
    - Allows the probe, or the baseline_engine or prediction_engine (on behalf of the probe), to compute hourly baselines that are based on QoS data.
Supported Threshold Types
The following threshold limit types are supported:
Static
- Alarms are sent when the configured time requirements for a QoS metric have exceeded the threshold. A static threshold is effectively a high pass filter.
If a probe does not support static alarms, you might see an Alarm Thresholds section on the configuration page.
Dynamic
- A dynamic threshold is calculated on variance from the calculated static baseline with no averaging. Variances can be set to one of the following algorithms:
  • Scalar
    - A set value past the calculated baseline
  • Percent
    - A set percent past the baseline
  • Standard Deviation
    - A set standard deviation past the baseline
The type of thresholds available vary by probe. Not all threshold types are supported by all probes. If a threshold type is not configurable in a probe configuration UI, the probe does not support that threshold type.
Configuring these dynamic alarms are only applicable for dynamic alarms that the baseline_engine probe generates. These configurations are not applicable for dynamic alarms that are configured through alarm policies and are generated by the spooler probe.
Running the threshold_migrator Probe
With
CA Unified Infrastructure Management
8.2, a new threshold_migrator probe is available. Using it, you can migrate probes to include the standard static alarm threshold parameters. After you migrate probes with threshold_migrator, the probes no longer generate alarms on thresholds. Instead, baseline_engine generates static, dynamic, Time Over Threshold, and Time to Threshold alarms when user-configured thresholds are breached.
After you migrate probes using the threshold_migrator, you can configure the migrated probes only in Admin Console. Configuration is no longer available in Infrastructure Manager. Once you use threshold_migrator to migrate probes, you cannot revert to the previous probe configuration.
After you migrate a probe, view the probe GUI in Admin Console. In the GUI, you see the settings that are now migrated to the appropriate static alarm fields.
Before you use the threshold_migrator probe, the latest version of the probe must be deployed to each target device.
For more information about using the threshold_migrator probe, see threshold_migrator (Threshold Migrator).
Configuring Alarm Thresholds
For some probes, you can configure both static and dynamic alarm thresholds. Some probes allow you to configure only dynamic alarm thresholds. Other probes support only high or low alarm thresholds. Use the following information to configure alarm thresholds, when required.
  • Configure the unit of measure. Choose the unit of measure for the aspect of a device that you want to monitor. For example, when you monitor Disk Usage with the cdm probe, enter
    percent
    in the
    Send Alarm Based on Threshold
    field.
  • Qualify the type of threshold. Depending on the probe, you configure one of or all the following parameters:
    • Enable the
      high
      threshold
      or
      low
      threshold
      options to indicate whether either threshold or both thresholds are evaluated. When the high and low threshold options are enabled, the high threshold is evaluated first. If the high threshold is not exceeded, then the low threshold is evaluated.
    • Select an
      operator
      value. The value can be
      greater than
      ,
      less
      than
      ,
      equal to
      , or a combination of these values.
    • If applicable, select a
      direction
      which can be either
      increasing
      or
      decreasing
      . The direction setting determines if an alarm occurs when monitored QoS data is
      greater than
      or
      lower than
      the threshold.
  • For each threshold enabled, enter a threshold value.
  • For each threshold enabled, select the alarm message to be displayed on CA Unified Service Manager or Infrastructure Manager. The alarm appears when monitored QoS data is lower, equal to, or higher than the configured threshold value.
Variable Substitution Supported with ppm 3.20 and Later
For some of the text string fields (such as the Custom Alarm Message field), you can enter the key identifier
${
. You can select variables from a drop-down list, or you can type a variable. Selecting a variable from a drop-down list makes it easier to supply the correct variable name for a custom message.
For example, for some elements that the cdm probe monitors, you can enter a Custom Alarm Message and Custom Alarm Clear Message. You can either type the variable name
${qos_name}
in the text field, or you can type the key identifier
${
and can select
qos_name
from the drop-down list. After you enter a variable, baseline_engine provides the actual value for the variable when a monitoring probe generates an alarm.
You can select one or more variables for a text string field in a custom alarm message. For example:
${qos_name} from source ${source} that is targeting ${target} is ${operator} the threshold of ${threshold}.
If you enter
${
and select a variable for a text field where the variables are displayed but not applicable (for example, the Subsystem field) the system ignores the variable.
Follow these steps:
  1. Go to a text string field and enter: ${
    You see a drop-down list of variables the baseline_engine substitutes or probe-specific variables.
  2. Select a variable.
    All baseline_engine attribute variables have the format ${<variable_name>.
  3. Configure the remaining settings and then save your changes.
Configuring Dynamic Alarm Thresholds
Dynamic alarm thresholds can be set at the QoS metric level in probes that publish alarms for a QoS metric.
To create dynamic alarm thresholds, first install the baseline_engine probe version 2.0 or later on the hub robot.
To set a Dynamic alarm, verify the version of the ppm probe on the hub robot. Then complete one of the following procedures:
For Hubs Running ppm v3.24 and Later
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click
    Publish Data
    ,
    Publish Alarms
    (if available), and
    Compute Baseline
    .
    If you cannot select the Compute Baseline box, click . If necessary, deploy or activate the baseline_engine probe.
  4. Click the
    Dynamic Alarm
    check box. The Dynamic Alarm options become available.
  5. Choose an Algorithm to use:
    • Scalar
      - Each threshold is a specific value from the computed baseline.
    • Percent
      - Each threshold is a specific percentage of the computed baseline.
    • Standard Deviation
      - Each threshold is a measure of the variation from the computed baseline. A large standard deviation indicates that the data points are far from the computed baseline. A small standard deviation indicates that they are clustered closely around the computed baseline.
  6. Choose an operator for the threshold:Set the threshold for each alarm state.
    • >
      An alarm occurs when the metric is greater than the set threshold.
    • > =
      An alarm occurs when the metric is greater than or equal to the set threshold.
    • <
      An alarm occurs when the metric is below the set threshold.
    • <  =
      An alarm occurs when the metric is below or equal to the set threshold.
    • =
      An alarm occurs when the metric is equal to the set threshold.
    • !=
      An alarm occurs when the metric is not equal to the set threshold.
  7. (Optional) Enter a different (overriding) Subsystem ID using the
    Subsystem (override) field
    . The override is only required if the Subsystem ID shown in the
    Subsystem (default)
    field is not correct for your configuration.
    The override option is available with baseline_engine 2.1 or later.
  8. (Optional) Create a custom alarm message for your environment:
    1. In the Custom Alarm Message field, enter or select variables to include in a custom message.The available variables are:${baseline} - The baseline that is calculated for a QoS metric when the
      Compute Baseline
      option is selected for the metricBaselines are not calculated for static messages. The baseline value is always zero for static alarms.${level} - The numerical severity level of the alarm. Valid values are: 1 (critical), 2 (major), 3 (minor), 4 (warning), or 5 (information).${operator} - The operator (>, >=, <, <=, ==, or !=) for the alarm severity level${qos_name} - The name of the QoS metric${qos_source} or ${source} - The source of the QoS metric that generated an alarm${qos_target} or ${target} - The target of the QoS metric that generated an alarm${qosReference} - Adds the name of the QoS metric for which the time-to-threshold is configured${tttTime} - Adds sample time (in numerals only) for which the time-to-threshold is configured${tttTimeUnit} – Adds the time unit of ${tttTimes}${tttValue} – Adds the user input time-to-threshold Prediction Value${predictionValue} – Adds the predicted time at which the ${tttValue} is crossed
      ${threshold} - Specifies the threshold upon which an alarm is generated${threshold_sign} – Use this variable
      before
      the ${threshold} variable. The ${threshold_sign} variable generates a + plus-sign when the threshold is a positive integer.${threshold_symbol} – Use this variable
      after
      the ${threshold} variable. The ${threshold_symbol} variable generates a percent symbol for dynamic percentage thresholds or a sigma symbol for dynamic standard deviation thresholds.${threshold_value} – If you want the evaluated threshold value, use this variable instead of the ${threshold} variable. For example, if the threshold is 5 percent of a baseline of 10, then the evaluated threshold value is 10.5.
      ${unit} - Specifies the unit of measure for the QoS value. For example, 50 ms (milliseconds).
      ${value} - Specifies the value that is contained in the generated QoS message
      For more information, see variable substitution.
    2. In the Custom Alarm Clear Message field, enter the message to display when the alarm clears.
      The available variables include:
      ${qos_name} - The name of the QoS metric
      ${value} - Specifies the value that is contained in the generated QoS message
      ${source} - The source of the QoS metric that generated an alarm
  9. Save your settings.
For Hubs Running ppm v3.11-v3.22
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click
    Publish Data
    ,
    Publish Alarms
    (if available), and
    Compute Baseline
    .
    If you cannot select the Compute Baseline check box, click . If necessary, deploy or activate the baseline_engine probe.
  4. Click the
    Dynamic Alarm
    check box. The Dynamic Alarm options become available.
  5. Choose an Algorithm to use:
    • Scalar
      - Each threshold is a specific value from the computed baseline.
    • Percent
      - Each threshold is a specific percentage of the computed baseline.
    • Standard Deviation
      - Each threshold is a measure of the variation from the computed baseline. A large standard deviation indicates that the data points are far from the computed baseline. A small standard deviation indicates that they are clustered closely around the computed baseline.
  6. Choose an operator for the threshold:
    • >
      An alarm occurs when the metric is greater than the set threshold.
    • > =
      An alarm occurs when the metric is greater than or equal to the set threshold.
    • <
      An alarm occurs when the metric is below the set threshold.
    • <  =
      An alarm occurs when the metric is below or equal to the set threshold.
    • =
      An alarm occurs when the metric is equal to the set threshold.
    • !=
      An alarm occurs when the metric is not equal to the set threshold.
  7. Set the threshold for each alarm state.
  8. (Optional) Enter a different (overriding) Subsystem ID using the
    Subsystem (override) field
    . The override is only required if the Subsystem ID shown in the
    Subsystem (default)
    field is not correct for your configuration.
    The override option is available with baseline_engine 2.1 or later.
  9. (Optional) Create a custom alarm message for your environment:
    1. In the Custom Alarm Message field, enter or select variables to include in a custom message. The available variables are:
      ${baseline} - The baseline that is calculated for a QoS metric when the
      Compute Baseline
      option is selected for the metricBaselines are not calculated for static messages. The baseline value is always zero for static alarms.
      ${level} - The numerical severity level of the alarm
      Valid values are: 1 (critical), 2 (major), 3 (minor), 4 (warning), or 5 (information).
      ${operator} - The operator (>, >=, <, <=, ==, or !=) for the alarm severity level
      ${qos_name} - The name of the QoS metric${qos_source} or ${source} - The source of the QoS metric that generated an alarm${qos_target} or ${target} - The target of the QoS metric that generated an alarm${qosReference} - Adds the name of the QoS metric for which the time-to-threshold is configured${tttTime} - Adds sample time (in numerals only) for which the time-to-threshold is configured${tttTimeUnit} – Adds the time unit of ${tttTimes}${tttValue} – Adds the user input time-to-threshold Prediction Value${predictionValue} – Adds the predicted time at which the ${tttValue} is crossed
      ${threshold} - Specifies the threshold upon which an alarm is generated${threshold_value} – If you want the evaluated threshold value, use this variable instead of the ${threshold} variable. For example, if the threshold is 5 percent of a baseline, which is 10, then the evaluated threshold value is 10.5.
      ${value} - Specifies the value that is contained in the generated QoS message
      For more information, see variable substitution.
    2. In the Custom Alarm Clear Message field, enter the message that is displayed when the alarm clears.
      The available variables include:
      ${qos_name} - The name of the QoS metric
      ${value} - Specifies the value that is contained in the generated QoS message
      ${source} - The source of the QoS metric that generated an alarm
  10. Save your settings.
For Hubs Running ppm v3.0
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click
    Publish Data
    ,
    Publish Alarms
    (if available), and
    Compute Baseline
    .
    If you cannot select the Compute Baseline check box, click . If necessary, deploy or activate the baseline_engine probe.
  4. Click the
    Dynamic Alarm
    check box. The Dynamic Alarm options become available.
  5. Choose an Algorithm to use:
    • Scalar
      - Each threshold is a specific value from the computed baseline.
    • Percent
      - Each threshold is a specific percentage of the computed baseline.
    • Standard Deviation
      - Each threshold is a measure of the variation from the computed baseline. A large standard deviation indicates that the data points are far from the computed baseline. A small standard deviation indicates that they are clustered closely around the computed baseline.
  6. Choose an operator for the threshold:
    • Greater than (>)
      - An alarm occurs when the metric increases past the set threshold.
    • Less than (<)
      - An alarm occurs when the metric falls below the set threshold.
  7. Set the threshold for each alarm state.
  8. Save your settings.
If you are using baseline_engine 2.1 or later, you can also change the Subsystem ID using the
Subsystem (override) field
. The override is only required if the Subsystem ID shown in the
Subsystem (default)
field is not correct for your configuration.
For Hubs Running ppm v2.38
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click the
    Publish Data
    box.
  4. Click the
    Compute Baseline
    box. The Dynamic Alarm Thresholds section is enabled.
  5. Change the drop-down in the Dynamic Alarm Thresholds section from
    None
    to
    Dynamic
    . The Dynamic Alarm Threshold section expands and more options become available.
  6. Choose an Algorithm to use:
    • Scalar
      - Each threshold is a specific value from the computed baseline.
    • Percent
      - Each threshold is a specific percentage of the computed baseline.
    • Standard Deviation
      - Each threshold is a measure of the variation from the computed baseline. A large standard deviation indicates that the data points are far from the computed baseline. A small standard deviation indicates that they are clustered closely around the computed baseline.
  7. Choose a direction for the threshold:
    • Increasing
      - An alarm occurs when the metric increases past the set threshold.
    • Decreasing
      - An alarm occurs when the metric falls below the set threshold.
  8. Set the threshold for each alarm state.
  9. Save your settings.
If you are using baseline_engine 2.1, you can also change the Subsystem ID using the
Subsystem (override) field
. The override is only required if the Subsystem ID shown in the
Subsystem (default)
field is not correct for your configuration.
Configuring Static Alarm Thresholds
You can set static alarm thresholds at the QoS metric level for some probes that publish alarms for a QoS metric. The following procedures explain how to configure some commonly used probes.
To create dynamic alarm thresholds, first install and configure the baseline_engine probe version 2.0 or later on the hub robot.
To set a Static alarm, determine the version of the ppm probe running on the hub robot. Then complete one of the following procedures:
For Hubs Running ppm v3.24 and Later
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
    Click
    Publish Data
    and
    Publish Alarms
    .
  3. Click
    Static Alarm
    . The Static Alarm options become available.
    If you cannot select the Static Alarm check box, click . If necessary, deploy or activate the baseline_engine probe.
  4. Choose an operator for the threshold:
    • >
      An alarm occurs when the metric is greater than the set threshold.
    • > =
      An alarm occurs when the metric is greater than or equal to the set threshold.
    • <
      An alarm occurs when the metric is below the set threshold.
    • <  =
      An alarm occurs when the metric is below or equal to the set threshold.
    • =
      An alarm occurs when the metric is equal to the set threshold.
    • !=
      An alarm occurs when the metric is not equal to the set threshold.
      If you used the threshold_migrator probe to add the static threshold fields for a probe, the operator and configured threshold carry over.
  5. Set the threshold for each alarm state.
  6. (Optional) Enter a different (overriding) Subsystem ID using the
    Subsystem (override) field
    . The override is only required if the Subsystem ID shown in the
    Subsystem (default)
    field is not correct for your configuration.
    The override option is available with baseline_engine 2.1 or later.
  7. (Optional) Create a custom alarm message for your environment:
    1. In the Custom Alarm Message field, enter or select variables to include in a custom message.
      The available variables are:
      ${baseline} - The baseline that is calculated for a QoS metric when the
      Compute Baseline
      option is selected for the metricBaselines are not calculated for static messages. The baseline value is always zero for static alarms.
      ${level} - The numerical severity level of the alarm
      Valid values are: 1 (critical), 2 (major), 3 (minor), 4 (warning), or 5 (information)
      ${operator} - The operator (>, >=, <, <=, ==, or !=) for the alarm severity level
      ${qos_name} - The name of the QoS metric${qos_source} or ${source} - The source of the QoS metric that generated an alarm${qos_target} or ${target} - The target of the QoS metric that generated an alarm${qosReference} - Adds the name of the QoS metric for which the time-to-threshold is configured${tttTime} - Adds sample time (in numerals only) for which the time-to-threshold is configured${tttTimeUnit} – Adds the time unit of ${tttTimes}${tttValue} – Adds the user input time-to-threshold Prediction Value${predictionValue} – Adds the predicted time at which the ${tttValue} is crossed.
      ${threshold} - Specifies the threshold upon which an alarm is generated${threshold_sign} – Use this variable
      before
      the ${threshold} variable to generate a + plus-sign when the threshold is a positive integer.
      ${threshold_symbol} – Use this variable
      after
      the ${threshold} variable to generate a percent symbol for dynamic percentage thresholds or a sigma symbol for dynamic standard deviation thresholds.
      ${threshold_value} – If you want the evaluated threshold value, use this variable instead of the ${threshold} variable. For example, if the threshold is 5 percent of a baseline, which is 10, then the evaluated threshold value is 10.5.
      ${value} - Specifies the value that is contained in the generated QoS message
      For more information, see variable substitution.
    2. In the Custom Alarm Clear Message field, enter the message that is displayed when the alarm clears.
      The available variables include:
      ${qos_name} - The name of the QoS metric
      ${value} - Specifies the value that is contained in the generated QoS message
      ${source} - The source of the QoS metric that generated an alarm
  8. Save your settings.
For Hubs Running ppm v3.11-v3.22
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
    Click
    Publish Data
    and
    Publish Alarms
    .
  3. Click the
    Static Alarm
    check box. The Static Alarm options become available.
    If you cannot select the Static Alarm check box, click . If necessary, deploy or activate the baseline_engine probe.
  4. Choose an operator for the threshold:
    • >
      An alarm occurs when the metric is greater than the set threshold.
    • > =
      An alarm occurs when the metric is greater than or equal to the set threshold.
    • <
      An alarm occurs when the metric is below the set threshold.
    • <  =
      An alarm occurs when the metric is below or equal to the set threshold.
    • =
      An alarm occurs when the metric is equal to the set threshold.
    • !=
      An alarm occurs when the metric is not equal to the set threshold.
      If you used the threshold_migrator probe to add the static threshold fields for a probe, the operator and configured threshold are carried over.
  5. Set the threshold for each alarm state.
  6. (Optional) Enter a different (overriding) Subsystem ID using the
    Subsystem (override) field
    . The override is only required if the Subsystem ID shown in the
    Subsystem (default)
    field is not correct for your configuration.
    The override option is available with baseline_engine 2.1 or later.
  7. (Optional) Create a custom alarm message for your environment:
    1. In the Custom Alarm Message field, enter or select variables to include in a custom message.
      The available variables are:
      ${baseline} - The baseline that is calculated for a QoS metric when the
      Compute Baseline
      option is selected for the metricBaselines are not calculated for static messages. The baseline value is always zero for static alarms
      ${level} - The numerical severity level of the alarm
      Valid values are: 1 (critical), 2 (major), 3 (minor), 4 (warning), or 5 (information)
      ${operator} - The operator (>, >=, <, <=, ==, or !=) for the alarm severity level
      ${qos_name} - The name of the QoS metric
      ${qos_source} or ${source} - The source of the QoS metric that generated an alarm
      ${qos_target} or ${target} - The target of the QoS metric that generated an alarm
      ${qosReference} - Adds the name of the QoS metric for which the time-to-threshold is configured
      ${tttTime} - Adds sample time (in numerals only) for which the time-to-threshold is configured
      ${tttTimeUnit} – Adds the time unit of ${tttTimes}
      ${tttValue} – Adds the user input time-to-threshold Prediction Value
      ${predictionValue} – Adds the predicted time at which the ${tttValue} is crossed
      ${threshold} - Specifies the threshold upon which an alarm is generated
      ${threshold_value} – If you want the evaluated threshold value, use this variable instead of the ${threshold} variable. For example, if the threshold is 5 percent of a baseline, which is 10, then the evaluated threshold value is 10.5.
      ${value} - Specifies the value that is contained in the generated QoS message
      For more information, see variable substitution.
    2. In the Custom Alarm Clear Message field, enter the message that is displayed when the alarm clears.
      The available variables include:
      ${qos_name} - The name of the QoS metric
      ${value} - Specifies the value that is contained in the generated QoS message
      ${source} - The source of the QoS metric that generated an alarm
  8. Save your settings.
For Hubs Running ppm v3.0
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click
    Publish Data
    and
    Publish Alarms
    .
  4. Click
    Static Alarm
    . The Static Alarm options become available.
    If you cannot select the Static Alarm check box, click . If necessary, deploy or activate the baseline_engine probe.
  5. Choose an operator for the threshold:
    • Greater than (>)
      - An alarm occurs when the metric increases past the set threshold.
    • Less than (<)
      - An alarm occurs when the metric falls below the set threshold.
  6. Set the threshold for each alarm state.
  7. Save your settings.
If you are using baseline_engine 2.1 or later, you can also change the Subsystem ID using the
Subsystem (override) field
. The override is only required if the Subsystem ID shown in the
Subsystem (default)
field is not correct for your configuration.
For Hubs Running ppm v2.38
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click the
    Publish Data
    box.
  4. Change the drop-down in the Static Alarm Thresholds section from
    None
    to
    Static
    .
  5. Choose a direction for the static threshold:
    • Increasing
      - An alarm occurs when the metric is greater than the set threshold.
    • Decreasing
      - An alarm occurs when the metric falls below the set threshold.
  6. Set the threshold for each alarm state.
  7. (Optional) If the Subsystem ID listed in the
    Subsystem (default)
    field is not correct for your configuration, enter the correct ID in the
    Subsystem (override)
    field.
  8. Save your settings.
Configuring Time Over Threshold
Using Time Over Threshold (TOT), you can create an alarm for an event based on how long it has exceeded a threshold.
To use Time Over Threshold, first install the following probe versions at each hub level where you want TOT:
  • alarm_enrichment 4.40 or later
  • baseline_engine 2.34 or later
  • nas 4.40 or later
  • Probe Provisioning Manager (PPM) 2.38 or later
  • prediction_engine 1.01 or later
To configure a Time Over Threshold alarm, determine the version of the ppm probe running on the hub robot. Then complete one of the following procedures:
For Hubs Running ppm v3.0 and Later
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Click
    Publish Data
    ,
    Publish Alarms
    , and
    Compute Baseline
    (for a dynamic alarm).
  4. Click either the
    Dynamic Alarm
    or
    Static Alarm
    check box.
    If you cannot select either of these boxes, click . If necessary, deploy or activate the baseline_engine probe.
  5. Configure the dynamic or static alarm settings. See dynamic alarms or static alarms for details.
  6. For either a dynamic or static alarm, select the
    Enable Dynamic Time Over Threshold
    or
    Enable Static Time Over Threshold
    check box.
  7. Enter values for the following fields:
    • Time Over Threshold <TOT>
      - The length of time a metric must remain over threshold before an alarm is sent.
    • Sliding Time Window <TW>
      -The length of time in the sliding window in which metrics are monitored for threshold violations.
    • Time Units for <TOT> and <TW>
      - The unit of measurement that is used by the
      Time Over Threshold
      and
      Time Window
      parameters. The measurement is in minutes, hours, or days. 
    • Automatically Clear Alarm
      - Enables the Auto-clear functionality.
    • Clear Delay Time
      - The length of time that is used in the Auto-clear timer. If no alarms are sent in the set time period, the alarm is automatically cleared.
    • Time Units for <TC>
      - The unit of measurement that is used by the Auto-clear. The measurement is in minutes, hours, or days. 
  8. Save your changes.
The following changes take effect immediately:
  • New Time Over Threshold rules.
  • Changes to the Clear Delay Time parameter
  • Changes to the Time Over Threshold active state
The following changes take effect at the next received alarm:
  • Changes to the Time Over Threshold parameter
  • Changes to the Sliding Time Window parameter
For Hubs Running ppm v2.38
Follow these steps:
  1. Select
    Publish Data
    and
    Compute Baseline
    .
  2. Configure a dynamic or static alarm threshold.
  3. For either a dynamic or static alarm, select the
    Enable Dynamic Time Over Threshold
    or
    Enable Static Time Over Threshold
    check box.
  4. Enter values for the following fields:
    • Time Over Threshold <TOT>
      - The length of time a metric must remain over threshold before an alarm is sent.
    • Sliding Time Window <TW>
      -The length of time in the sliding window in which metrics are monitored for threshold violations.
    • Time Units for <TOT> and <TW>
      - The unit of measurement that is used by the
      Time Over Threshold
      and
      Time Window
      parameters. The measurement is in minutes, hours, or days. 
    • Automatically Clear Alarm
      - Enables the Auto-clear functionality.
    • Clear Delay Time
      - The length of time that is used in the Auto-clear timer. If no alarms are sent in the set time period, the alarm is automatically cleared.
    • Time Units for <TC>
      - The unit of measurement that is used by the Auto-clear. The measurement is in minutes, hours, or days. 
  5. Save your changes.
The following changes take effect immediately:
  • New Time Over Threshold rules
  • Changes to the Clear Delay Time parameter
  • Changes to the Time Over Threshold active state
The following changes take effect at the next received alarm:
  • Changes to the Time Over Threshold parameter
  • Changes to the Sliding Time Window parameter
Configuring Time to Threshold
Time to Threshold is set at the QoS metric level in the probes that publish alarms for QoS metrics.
To use Time to Threshold, first install the following probe versions at the secondary hub level:
  • baseline_engine 2.34 or later
  • Probe Provisioning Manager (ppm) 2.38 or later
  • prediction_engine 1.01 or later
To configure a Time to Threshold alarm, determine the version of the ppm probe running on the hub robot. Then complete one of the following procedures:
For Hubs Running ppm v3.0 and Later
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Select the
    Publish Data
    and
    Publish Alarms
    (if available) to publish QoS data from monitoring probes to the message bus.
  4. (Optional) Select the
    Compute Baseline
    check box if you want baseline_engine to compute hourly baselines that are based on QoS data.
    If you cannot select the Static Alarm check box, click . If necessary, deploy or activate the baseline_engine probe.
  5. Select the
    Time to Threshold
    Alarm
    check box to configure a Time to Threshold alarm.
    If you cannot select the Static Alarm check box, click . If necessary, deploy or activate the baseline_engine probe.
  6. Configure the alarm settings.
    • Time Units:
      Select day or hours as the unit of time.
    • Prediction Value:
      Enter an appropriate value for the QoS metric. For example, 50 to indicate the percent for Disk Usage.
    • Alarm Severity:
      Select the level alarm generated.
      • Critical Level 5
      • Major Level 4
      • Minor Level 3
      • Warning Level 2
      • Information Level 1
  7. Save your changes.
For Hubs Running ppm v2.38
Follow these steps:
  1. In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
  2. Select the monitor that you want to modify from the available list.
  3. Select the
    Publish Data
    check box to send the QoS data.
    You must select the Publish Data check box before you can configure the Time to Threshold settings.
  4. Select
    Time to Threshold Alarm
    in the Predictive Alarm drop-down list.
  5. Configure the predictive alarm settings.
    • Time Threshold:
      enter a number to indicate the number of hours or days within reaching the configured prediction value.
    • Time Units:
      Select days or hours as the unit of time.
    • Prediction Value:
      Enter an appropriate value for the QoS metric. For example, 50 to indicate the percent for Disk Usage.
    • Alarm Severity:
      Select the level alarm generated.
      • Critical Level 5
      • Major Level 4
      • Minor Level 3
      • Warning Level 2
      • Information Level 1
Create Baselines and Threshold for Probes Without Using the Web-Based GUI
Instead of using a probe GUI, you can use the <baseline_engine_dir>. For more information, see the topic baseline_engine Configuration.