Creating Corrective Actions for Metrics

For any target, the Metric and Collection Settings page shows whether corrective actions have been set for various metrics. For each metric, the Corrective Actions column shows whether Critical and/or Warning severities of corrective actions have been set.

  1. From any target's home page menu, select Monitoring, then Metric and Collection Settings. The Metric and Collection Settings page appears.

    Tip:

    For instance, on the home page for a host named dadvmn0630.myco.com, you would select the Host menu, then Monitoring, then Metric and Collection Settings.

  2. Click the pencil icon for a specific metric to access the Edit Advanced Settings page for the metric.
  3. In the Corrective Actions section, click Add for the metric severity (Warning and/or Critical) for which you want to associate a corrective action.
  4. Select the task type on the Add Corrective Actions page, then click Continue.

    • If you want to use a corrective action from the library, select From Library as the task type. Using a library corrective action copies the description, parameters, and credentials from the library corrective action. You must still define a name for the new corrective action. You can provide corrective action parameters if necessary.

    • If you want to create a corrective action to store in the library, see Creating a Library Corrective Action.

    • If you want to provide an Agent-side response action, select Agent Response Action as the task type. See Providing Agent-side Response Actions for more information.

  5. On the Corrective Action page, provide input for General, Parameters, and Credentials as you would similarly do when creating a job.
  6. Click Continue to save the corrective action and return to the Edit Advanced Settings page, where your corrective action now appears.
  7. Optional: To prevent multiple instances of a corrective action from operating simultaneously, enable the Allow only one corrective action for this metric to run at any given time checkbox.

    This option specifies that both Critical and Warning corrective actions will not run if a severity is reported to the Oracle Management Services when an execution of either corrective action is currently running. This can occur if a corrective action runs longer than the collection interval of the metric it corrects; the value of the metric may be oscillating back and forth across one of the thresholds (leading to multiple executions of the same corrective action), or may be rising or falling quickly past both thresholds (in which case an execution of the Warning corrective action may overlap an execution of the Critical corrective action).

    If you do not select this option, multiple corrective action executions are launched under the aforementioned circumstances. It is the administrator's responsibility to ensure that the simultaneous corrective action executions do not conflict.

  8. Click Continue when you have finished adding corrective actions to return to the Metric and Collection Settings page.

    The page shows the corrective action value you have provided for the metric in the Corrective Actions column. Possible values are:

    • None — No corrective actions have been set for this metric.

    • Warning — A corrective action has been set for Warning, but not Critical, alerts for this metric.

    • Critical — A corrective action has been set for Critical, but not Warning, alerts for this metric.

    • Warning and Critical — Corrective actions have been set for both Warning and Critical alerts for this metric. If an Agent-side response action is associated with the metric, the value is also Warning and Critical, since Agent-side response actions are always triggered on either Critical or Warning alert severities.

  9. Continue the process from step 2 forward, then click OK on the Metric and Collection Settings page to save your corrective actions and return to the target page you started from in step 1.