Adding an Alert Action (CLI)

Specify one or more events and specify responses to alerts for those events. More than one alert action can be specified for a particular event alert.

Go to configuration alerts actions and enter the create command.
```
hostname:configuration alerts actions> create
```
Set the category property.
See Alert Event Categories or enter set category= followed by a tab character to see the list of available event categories.

Specify one of the following:
- The all category - Enter show to see the list of events in this category. By default, all events are set to true, so the alert action will be performed for all events in the category. If this alert action should be performed for only a subset of events, change to false the events that should not cause this alert action to be performed.
- A specific category, such as hardware_faults or smf - Enter show to see the list of events in this category. By default, all events are set to true, so the alert action will be performed for all events in the category. If the alert action should be performed for only a subset of events, change to false the events that should not cause this alert action to be performed.
  The analytics category enables you to select high-level events such as datasets auto-suspend warning, memory total exceeded, and usage exceeded. To define an alert for a threshold condition for a specific statistic, see Adding a Threshold Alert (CLI).
  
  The thresholds category does not enable you to specify threshold events. The thresholds category requires that you specify an existing threshold event alert. To define an alert for a threshold condition for a specific statistic, see Adding a Threshold Alert (CLI). To define an alert action that is specific to a particular statistic threshold event, add a threshold alert action as described in Adding an Action for a Specific Threshold Alert (CLI). To define an alert action for high-level threshold events such as statistic threshold violated, use the Thresholds category in the BUI procedure Adding an Alert Action (BUI).
- The custom category - The custom category enables you to define an alert action for an event that you define in a workflow. See Adding an Alert Action for an Event Defined in a Workflow (CLI).
Enter commit.
Enter list to see the list of all configured alert actions.

The new alert action should be at the bottom of the list and should have a name (actions-### ) and a category, but no action or handler.

Select the new alert action.

hostname:configuration alerts actions> select actions-001
hostname:configuration alerts actions-001>

Set the alert handler. Enter action and then enter get.

hostname:configuration alerts actions-001> action
hostname:configuration alerts actions-001 action (uncommitted)> get
                       handler = email
                       address = (unset)
                       subject = (unset)

The default handler is email. If you want a different handler, enter set handler= followed by a tab character to see the list of possible handlers.

Set values for any handler arguments.
1. Enter get again to see the list of arguments, if any, for the specified handler.
2. Most of the actions have arguments. For example, you might have to specify an email recipient, dataset, or workflow.
Enter commit.

Enter list to confirm that the action is correct.
Enter done.

Enter list to view the list of actions.

Next Steps

To change which events are included in this alert action, enter select actions-###, set the events to true or false, and enter commit.
To specify additional actions for this alert action, enter select actions-###, and repeat step 6 through step 9. Additional actions are shown on separate lines for the specified actions-###.
To delete an alert action, enter destroy actions-### and enter y to confirm.