A log file monitor rule consists of the following components:
Search criteria — The core elements of log file rules. A search criterion allows you to create and store exactly what data a log file resource monitor will look for when it searches a log file. OpenEdge Management- and user-defined search criteria are stored in the library so they can be shared and reused in various log file monitor rules.
Severity — One of the four standard, user-selected severity levels: Information, Warning, Error, or Severe. This information is stored in the Severity field.
Alert — Identifies which action OpenEdge Management performs when an alert occurs. This user-selected information is stored in the On Alert Perform Action field.
You can include a rule in the log file resource monitor in three ways:
By adding it to a single log file resource under the resource's monitoring plan, in which case the rule definition cannot be shared by other log file resource monitors.
By adding it to one or more rule sets, in which case the rule can be shared among several log file resource monitors.
Note: Edits to any user-defined search criteria immediately affect all current instances in which the search criteria is used in individual rules or rule sets. These edits will also be used in instances created in the future. You can edit or delete OpenEdge Management-supplied search criteria.
Associating it with a log file resource monitor. An identical rule definition, defined in a rule set, can also be applied to this same log file resource monitor. In this situation, the individual, or locally defined rule, takes precedence. The rule definition associated with the rule set will be listed as part of the rule set, but the status icon for this duplicate rule will be gray and the status will be listed as Inactive.
Search criteria — The core elements of log file rules. A search criterion allows you to create and store exactly what data a log file resource monitor will look for when it searches a log file. OpenEdge Management- and user-defined search criteria are stored in the library so they can be shared and reused in various log file monitor rules.