Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Creating Threshold Crossing Alerts

    Creating a new threshold crossing alert involves two steps: 1) For the desired element type, create a scope identifying a subgroup of elements in which to place the rule. The scope can be used, for example, to filter on only fast ethernet interfaces, or events at a particular node. 2) Next, create the rule itself.


    Creating a New Scope


    To create a new scope, first select the upper level tree item under which the group will be created. Then either click the Create button in the top toolbar, or right-click the selected item and select Create.

    This will create a new group under that item. Select the new group and fill in the fields for the new group on the right pane. To enter text into a field, first double click the field to enable editing of the field.

    • Enter in a Scope Name (required) which will describe the scope of the rules contained within the group. Do not include any spaces in the name. Optionally, enter in a description of the scope in the Description field.
    • The Include and Exclude condition fields are preliminary filters for all rules within the group. Only data matching these conditions will be considered by the rules within the group. For example, you could set “name ~= fe” in the Include condition for an Interface scope to only consider fast ethernet interfaces. To edit these conditions, right-click at the beginning of the field to open the Condition and Rule Builder. For more information on how to define conditions, please see Defining Conditions and Rules. If you do not require any filtering, leave these fields blank.
    • The Is Active checkbox can be used to activate or deactivate the scope and the production rules underneath it. Only if both the scope and production rule is activated will the threshold event be generated.
    • The production count is the number of rules within the group.

    Creating a New Rule


    To create a new rule underneath a scope, first select the scope under which the new rule will be created. Then either click the Create New Production Rule button in the top toolbar, or right-click the selected item and select Create. This will create a new rule under the selected group.

    • Enter in a Production Name (required) to describe the threshold rule. Do not include any spaces in the name.
    • Enter in a Production Rule (required) to define the threshold crossing alert. If incoming data matches this rule, it will trigger the threshold event. Right-click at the beginning of the field to open the Condition and Rule Builder. An example rule for a production rule underneath the Interface scope is “ingressUtil > 75 || egressUtil > 75”. For more information on how to define conditions, please see Defining Conditions and Rules.
    • The Is Active checkbox can be used to activate or deactivate the production rule. Only if both the scope containing the production rule and the production rule is activated will the threshold event be generated.
    • The Event Type is the type of event triggered by this rule, which is displayed in the Event Browser when the threshold crossing alert is created. The default is ThresholdEvent and does not need to be changed. It can be helpful, however, to mark the events with more descriptive event types, such as ThresholdUtilizationEvent and ThresholdMemoryEvent. To define your own categories, see Defining New Threshold Event Categories.
    • The Severity selection is used to configure the severity of the event. This severity can later be viewed in the Event Browser when the Threshold Event is triggered.
    • The Source ID will be displayed as the source of the event triggered by this rule. This field corresponds to the Source ID field in the Event Browser.
    • Finally, the Description Template is used to describe the event triggered by this threshold rule. This is the primary means of specifying threshold event details in the Event Browser. The template allows for specifying keys and dynamic values by enclosing them within square brackets []. For a list of available suggestions while typing in the Description template field, right-click in the beginning of the field. For example, for a rule that triggers an event when ingress utilization or egress utilization exceed 75 percent, the following template may be used:
      [deviceID]: [name]: ingress util [ingressUtil] or egress util [egressUtil] greater than 75%

    Modified: 2016-11-08