Alert properties are located on the Rule Definition section of a resource's Rule: <Rule name> page. Review and update the values associated with these alert properties as you edit a rule for a resource.

The following procedure reviews the steps to edit a rule, noting the location and use of the alert properties with the help of an example of an AppServer instance.

To edit a rule for an AppServer instance:

  1. In the OpenEdge Management console menu, choose one:
    • Select Library > View > Rule Sets.
    • Select Library > Go to Library > View Rule Sets.
    The Library.Rule Sets page appears
  2. Type AppServer or its instance name in the Name field and select it.
    The Library.Rule Sets.AppServer page appears.
    Note: While searching for an instance of a resource, if you do not find the required instance, click Filter icon next to Name field to change the filtering option and repeat step 2.
  3. Click a rule set assigned to the resource monitor. If you have not added any rule set, click Default_AS_RuleSet.
    The AppSever Rule Set: <Default_AS_RuleSet> page appears.
  4. Click a rule listed in the Rules selected for this Rule Set section. For example, Abnormal Shutdown.
    The Rule: <AppServer Abnormal Shut Down> page appears.
  5. Click Edit. In the Rule Definition section, you can edit alert properties.

    The following table guides you in reviewing and updating values associated with the alert properties:

    To change this alert property . . . Perform this action . . .
    Threshold Type the recommended threshold value. See Set threshold values for more information.
    Alert Severity Select the drop-down list option to display the four severity options: Information, Warning, Error, and Severe.
    Throw alert after Type the number of failed polls after which an alert should fire. (For most resources, the default value is 1. However, the default value for network resource monitors is 2.)

    To minimize noise, consider setting this property to a low number for critical resources and to a higher number for less critical resources.

    Note: This property is not applicable to all resource monitors and does not appear on every resource property page.
    Throw additional alerts Choose when OpenEdge Management will throw additional alerts. Possible values are after a clear or specific number of failures.
    On alert perform action Select the drop-down list option to display the five actions: Default_Action, Default_Clear Action, Default_Mail_Action, Default_Pager_Action and Default_Task_Action. Select an action that OpenEdge Management will take when an alert is generated. The default is Default_Action.
    Clear alert after Enter one of the following possible values to indicate when you want an alert to be cleared once the condition that prompted the alert has been resolved:
    • 0 — The alert is not cleared automatically. You must manually clear all alerts.
    • 1 — The alert is automatically cleared the first time the resource successfully passes a poll.
    You can alternatively type a value greater than 1 to indicate that the alert will not be cleared until the resources passes this specified number of consecutive polls. This can prevent anti-noise from clearing an alert prematurely.
    On clear perform action Select a user-defined action or a compound action. For example, OpenEdge Management might run a job that was defined as an action. The default is None.
    Always throw new alert Mark the check box to fire an alert each time the alert is triggered. Clear the check box to fire the alert once, so that an alert message does not display in the user interface each time the alert is triggered.
  6. Click Save.
    Any changes made to the alert properties appear on the updated Rule: <AppServer Abnormal Shut Down> page.