Skip to Content

Filling out the Consider These Records dialog box

On this dialog box, define the subset of records that you want to consider for the alarm definition by specifying filter values. The filter values narrow the values and conditions you are monitoring.

MAKEALARM wizard


Related topics

Creating-an-alarm-definition-by-using-the-MAKEALARM-wizard

Using-active-alarms


Warning

Important

The fields shown on the Consider These Records dialog box are dependent on the view selected in the BMC AMI Ops product when you create the alarm. The values in the MAKEALARM wizard come from the context, parameters, column filters, Where clauses, and QWhere clauses of the selected view. Depending on the selected view, you might not have all the items displayed on the Consider These Records dialog box.

  1. Accept the default values or specify alternate values. The fields in the dialog are described in the following table.
  2. Click Next to continue to the next step in the MAKEALARM wizard (Filling-out-the-Use-These-Conditions-dialog-box).

Field descriptions for the Consider These Records dialog

Field

Default value

Information to specify

Unique AES=NO|YES

NO

Whether to run the alarm in a separate Alarm Evaluation Set

Possible values are NO (the default) or YES.

Some products (for example BMC AMI Ops Monitor for MQ) use parameters and column filters to pre-filter data on some views. If the filter is present these views, only data that matches that filter is presented to MVI for alarm evaluation. It is important that Alarms that use these pre-filters be run in separate evaluation sets. There is currently no way for Alarm Management to determine when the product is doing this pre-filtering.

If you suspect or are advised that you are having problems because multiple alarm definitions are run in a single Alarm Evaluation Set, you should set the value of this parameter to YES and re-activate the alarm. If you set Unique AES to YES, the alarm evaluator will run in a separate task and cannot be affected by other alarm definitions.

Context= context

currentContext

Target or SSI Context for the alarm definition.

By default the current context is entered. Summary views can only be used in target mode. Summary views are not allowed in SSI Contexts.

Parameters

No default

Parameters from the view.

Parameters are the column filters that can be overridden when invoking the view. You can change the parameter values in the alarm definition. We recommend that you specify the parameters you intend to use prior to creating the alarm. Defining the parameters first ensures that the records displayed in the view are the records you want to consider in the alarm definition.

Column filters

No default

Column filters

The Column Filters show you the filters from the view. If you have already set conditions for a column, the condition is shown in this field.

We recommend that you specify the parameters you intend to use prior to creating the alarm. Defining the parameters first ensures that the records displayed in the view are the records you want to consider in the alarm definition.

Where

No default

Where clause specifies complex filter conditions that are applied in addition to the column filters.

For alarm definitions based on views that are not summarized, there is no difference in the handling of Where and QWhere. The Where statement is the AND of any Where and QWhere. We recommend that you have the Where clause in effect before you create the alarm. This ensures that the records displayed in the view are the records you want to consider in the alarm definition. For more information on Where statements, seeQWHERE and WHERE commands.

QWhere

No default

(QWhere is only shown on the dialog if the alarm is based on a summary view.) QWhere clause specifies complex filter conditions that are applied to base records to be summarized.

To ensure that the records displayed in the view are the records you want to consider in the alarm definition, we recommend that you have the QWhere clause in effect before you create the alarm. For more information on QWhere statements, seeQWHERE and WHERE commands.

Information
Examples

The following examples show some common usage of QWhere and Where statements.

  • To filter values beginning with J or M in the field with an element of ELEMENT, use the following: (ELEMENT IN (j*,m*))
  • To filter values between 5.0 and 60.5 in the field with an element of ELEMENT, use the following: (ELEMENT BETWEEN 5.0 AND 60.5)
  • To filter values with T in the field with an element of ELEMENT and values between 2 and 25 in the field with an element of ELEMENT2, use the following: (ELEMENT = T) AND (ELEMENT2 BETWEEN 2 AND 25)
  • To filter values with an average greater than 60 in the field with an element of ELEMENT, use the following: ELEMENT:AVG > 60
  • To filter values with a maximum greater than 80 in the field with an element of ELEMENT, use the following: ELEMENT:MAX > 80
  • To filter values with a minimum less than 20 in the field with an element of ELEMENT, use the following: ELEMENT:MIN > 20

Schedule

Evaluate every nn seconds

60


Frequency (in seconds) of how often the alarm definition is evaluated

The frequency must be a multiple of five seconds and a minimum of five seconds. 

The frequency is the single most important factor in the amount of CPU used in the evaluation of alarm definitions. A lower number will use more CPU. A higher number will use less CPU.

Start

00:00

Periods for the alarm evaluation on various days of the week

Specify start and stop times for the alarm evaluation. Up to four periods can be specified.

A period can specify start/stop times for every day of the week, or for individual days of the week, but not both. If the start time is later in the day than the stop time, the alarm definition is presumed to span midnight. The period will start on the day specified, and stop at the stop time on the following day.

Stop

23:59

 

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

BMC AMI Ops User Interface 2.5