Alert Policy Wizard
The Alert Policy Wizard consists of four panels.
Table: Alert Policy Wizard General Panel
Setting | Description |
|---|---|
|
|
Enter a name for the alert policy. The name must be unique. Name is a required field. |
|
|
Enter a description for the alert policy. |
|
|
Select an alert condition from the list of alert conditions that are available. |
Table: Alert Policy Wizard Alert Condition Properties Panel
Setting | Description |
|---|---|
|
|
Specify attributes for the alert condition that you selected. The attributes differ for each alert condition. For many alert conditions (for example, for the Job Finalized condition), you may need to enter threshold attributes and other required or optional attributes. These attributes define and limit the alert. For alert conditions like High Job Failure Rate and Job Finalized, you may need to enter values for Exit Status to Include or Exit Status to Exclude field. You can provide multiple values in this field that are separated by comma in the following format: 20-35, 36, <40, >50 A value can be a range of exit status like 20-35 or all exit status below 40 like <40. Any combinations of this format can be used like 20-40, >55 or >70, 76 |
Table: Alert Policy Wizard Scope Panel
Setting | Description |
|---|---|
|
|
Select the view that should be verified for the alert condition. You can select a view and a node that contains a group of primary servers and also specific objects. For example, you can select the default view ALL PRIMARY SERVERS to be checked for the alert condition. When you select a view like ALL PRIMARY SERVERS or a node that contains a group of primary servers, all the primary servers that are currently in the view or node are automatically selected. In addition, primary servers that you may add later to this view or node are automatically selected and hence verified for the alert condition. You may also select only specific objects of a particular view or node to be checked for the alert condition. For example, you may select only a specific primary server(s) under the default view ALL PRIMARY SERVERS to be checked for the alert condition. To select a specific primary server, first deselect the view or node that contains the primary server and then select the primary server. You may also deselect a specific primary server from a view by selecting the view and then deselecting the specific primary server. Consider a scenario where there are two objects server A and server B in a particular view like ALL PRIMARY SERVERS. In case, you have selected the view and then specifically deselected server B , and in addition if you have selected a view or node that also contains server B, server B is not verified for the alert condition even though it is a part of the selected view or node. This is because you have specifically deselected server B from the view. When you specifically deselect a primary server from a view, which is also part of another selected view, the deselection or exclusion is given a higher priority because of which the primary server is not verified for the alert condition. For this reason, it is recommended that you do not repeat a primary server across groups. Note that you can also view and select additional attributes like policies, clients, media servers etc. on expanding the views and nodes from this page (wherever applicable). These attributes are located under the applicable views or nodes for specific alert conditions. For example, for the Job Finalized alert condition, you can select the view as well as the specific policies and clients that should be checked for the alert. You can view the applicable attributes like policy name, client name, media server name, robot number, drive IDs etc. for the following alert conditions:
You must select at least one object, node, or view from this page. |
Table: Alert Policy Wizard Actions Panel
Setting | Description |
|---|---|
|
|
Select email recipients to receive the alert notification. |
|
|
Select SNMP recipients to receive the alert notification. |
|
|
Select a severity level from the drop-down list. (If this alert occurs, the alert is displayed in the view.) |
|
|
Select an appropriate severity level from the drop-down list. With option, you can configure the severity for an email or trap that is sent when an alert is cleared. The default severity level is Informational. In OpsCenter, an alert is raised with the severity specified in the alert policy. Whenever this alert is cleared, an email or trap informing the user that the alert is cleared is sent with the same severity that is defined in the alert policy. This is the default behavior. For example, you may have created an alert policy for a Hung Job alert condition with a Critical severity. As a result, you receive Hung Job alert with Critical severity. When this Hung Job alert gets cleared, you receive an email or trap that informs you that the alert has been cleared. This email or trap also has a Critical severity. You can now configure the severity for this email or trap from Critical to some other severity like "Informational" while creating the alert policy. Note that you can configure the severity only for email or trap. |
|
|
The option is checked by default. By default, the policy will be active once you create it. Deselect the option if you want to deactivate the policy. You can always activate or deactivate the policy later from the OpsCenter console. See Managing an alert policy . |
More Information