Alert Management Administration › Exempt Alerts from Impact Analysis › Exempt Alerts with Event Management

Exempt Alerts with Event Management

You can use the Event Management UI to exempt alerts from the impact analysis calculations. To do so, you define criteria in the Event Management UI that matches a certain class of alerts and then specify the exempt action. Specifying the exempt action sets the isExempt property to true, which implies that the alert is not considered for any impact calculations.

For example, consider a scenario where the CA SystemEDGE monitoring generates alerts (through CA Spectrum) on FileSystem D: due to low space. The FileSystem is not modeled within CA SOI as a separate CI, but rather is managed as part of a ComputerSystem CI. The customer understands that this FileSystem does not impact any services in the infrastructure, and wants to prevent the alert from participating in the CA SOI state management. The event management enhancement enables you to define criteria that matches these FileSystem alerts (for example, matches(Summary, 'FileSystem D:')), and specify an associated exempt action.

Note: For more information about how to work with event policies, see the Event Management sections.

Follow these steps:

1. Open the Operations Console, and select Tools, Event Policies.
2. Specify the criteria that you want to use.

   For example, specify matches(Summary, 'FileSystem D:') in the Event Pattern 1 field of the Search Criteria section for the example scenario.

3. Click Create Policy.

   Note: Only one user can create an event policy at one time. If any other logged in user has the Create Event Policy wizard open, an error message appears saying that another user has a lock on the functionality. The user must close the dialog before you can create event policies.

4. Enter a name in the Policy Name field, and select the Exempt Event option.

   Note: The policy name cannot have more than 128 characters. Also, the name cannot contain any characters listed as prohibited on the tooltip that appears when you hover over the Policy Name text.

5. Click Next.

   The Select Data Sources page opens.

6. Perform one of the following steps:
   • Select the Save policy only option, and click Finish.

     The policy is saved but not deployed, and it appears in the Saved Policies section of the Events tab. This policy does not dynamically evaluate and process events according to its defined search patterns and resultant actions until you deploy it. Skip the rest of this procedure if you want to save the policy without deploying.

   • Select the Save and Deploy policy option.

     The list of available connectors becomes available.

7. Select the connectors on which to deploy the policy, move them to the Selected Data Sources pane, and click Finish.

   The policy is created, and it appears in the Deployed Policies section of the Events tab and under the appropriate data source in the Data Source section. After the policy is deployed to a connector, you can check the connector extensions (SOI_HOME\Core\CatalogPolicy\extensions) to verify that a policy extension, where the Exempt Event action was selected, exists. The naming convention for the policy extension file is ConnectorPolicyName.EventPolicyName.xml.