Alert Management Administration › Exempt Alerts from Impact Analysis › Exempt Alerts with Customized Connector Policy

Exempt Alerts with Customized Connector Policy

To have a connector set the isExempt property, customize the connector policy (SOI_HOME\resources\Core\Catalogpolicy\name_policy.xml). You can customize the policy by adding a normalization mapping rule to the connector Alert EventClass.

Note: For more information about the normalize policy operation, see the Connector Guide.

Follow these steps:

1. Navigate to the SOI_HOME\resources\Core\Catalogpolicy folder and locate the connector policy file; for example, spectrum_policy.xml.
2. Open the policy file in a text editor.
3. Add the normalization mapping rule. An example snippet is provided as follows:

   <EventClass name='Alert'>
      <Normalize>
      ...
        <Field output='isExempt' type='map' input='someProperty'>
          <mapentry mapin=’someRegexPattern' mapout='true'/>
          <mapentry mapin='.*' mapout='false'/>
        </Field>
      ...
      </Normalize>
   </EventClass>
   

   This mapping rule causes the policy to compare the input (someProperty) with the specified pattern (someRegexPattern). If the value of someProperty matches the regular expression (Regex) specified in someRegexPattern, the property isExempt is set to true. You can define any number of map entries to allow multiple Regex patterns to be easily mapped. If no entry is matched, the policy assigns the default value false, which implies that the alert participates in the impact analysis.

4. Save the changes in the policy file.
5. Restart the CA SAM Integration Services service.