https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=113214&_ga=2.185315433.1737315352.1582550490-1769026000.1575292893
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.
For Hubs Running ppm v3.24 and Later
-
In the probe GUI, select a node in the tree to view any associated monitors and QoS metrics.
-
Select the monitor that you want to modify from the available list.
Click
Publish Data
and
Publish Alarms
.
-
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.
-
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.
- Set the threshold for each alarm state.
-
(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.
-
(Optional) Create a custom alarm message for your environment:
-
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.
-
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
-