Health Metric Rules Configuration

You can configure health metrics for none, some, or all types of cluster members.

First, specify the cluster member for which a set of rules will apply. Then configure the individual rules. You can use either of the following as the basis of the rule:

  • A characteristic of the specified member’s child cluster members: either the number that is active or inactive, or their health level.
  • The specified cluster member’s number and frequency of alerts at a certain severity.

When setting up a health metric rule, put the most severe health level first. Within each clustermember element, the MM server examines the setproperty element that is closest to the top of the file first. When a health metric threshold for a cluster member is met, the application stops and does not process additional thresholds for that member.

If you configure all three levels, put critical first, then warning, and finally normal.

See Health Metric Rule Configuration Reference for more details on the settings referenced in this procedure.

Note: As with any procedure that changes files, ensure the emonitor project is backed up before you edit its CDD file.