Configuration Profiles

An alert criteria is called a configuration profile (config profile).

You can create a config profile and associate it with alert configurations, such as notification profiles, alert modifiers, and custom views. This ensures that the configurations apply only to alerts that meet the criteria.  

To create a configuration profile,

• Go to the required notification profile/alert modifier/custom view configuration page. 
• Click the gear icon  next to the Config Profile field, and click + Add. 
• In the slide-out, configure the following: 

Field	Description
Config Profile Name *	Give the configuration profile a name.
Applications *	Select the applications to which the configuration profile must be applied. You can apply the configuration profile to all or specific applications.
Criteria Configuration *	Use this section to configure alert criteria. You can configure one or more criteria groups, and combine them by AND/OR logic. In each criteria group, you can configure one or more conditions, and use the ALL/ANY toggle to define whether the alert must meet all or any condition within the group. • Configure conditions by selecting the alert attribute, operator, and value.  • To add multiple conditions within a group, click the plus icon .  • To remove a condition, click the minus icon . To add another group, click Add and select AND or OR to define whether the alert must satisfy all or any criteria group. To remove a group, click Delete below it. Click here to learn the rules to enter attributes, operators, and values.
Defined Criteria	The configured criteria is displayed as a logical expression.

*mandatory

Finally, click Add.

Edit Config Profile

To edit a config profile,

• Select it from the Config Profile drop-down in the configuration page. 
• Click the gear icon next to the field. 
• Click Edit. 

Clone Config Profile

To create a config profile similar to an existing one,

• Select an existing config profile from the Config Profile drop-down. 
• Click the gear icon next to the field, and click Clone.
• Make changes to the cloned profile and save it to add as a new config profile.

Rules to Enter Criteria Attributes

The attributes for defining criteria are available based on the applications you select.
For example, if you select AppManager, you can configure criteria by using AppManager-specific attributes, such as Health Severity, Annotations, Short Message, etc.

When multiple applications are selected and attributes from different applications are included within a group, do not use the Match ALL operator for that group.

Each application has its own set of attributes, and an alarm generated from one application may not contain attributes from another application. Therefore, using Match ALL expects all selected attributes to be present in a single alarm, which may cause the condition to fail.

The recommended approach is to:

• Use Match ANY when attributes from different applications are used within the same group. 
• Or, create separate groups for each application to ensure accurate rule evaluation.

Rules To Enter Criteria Attribute Values

While entering attributes values, you can use special characters as follows:

Special Character: Asterisk *  

Purpose: To check for multiple characters.

Example:

• alarm* : Checks for values that start with alarm.
  Example: alarmsone, alarm, etc.
• *one* : Checks for values that contain one.
  Example: alarmsone, oneauth, one, etc.
• *server : Checks for values that end with server.
  Example: webserver, server, etc.
• alarm* , *server, or *server alarm* : Checks for values that contain words starting with alert and ending with server.
  Example: alarmsone webserver is up, appserver alert in alarmsone, etc.

Special Character: Question mark ? 

Purpose: To check for exactly one character.

Example: nfa-pre-w? matches nfa-pre-w7, but not nfa-pre-w28.

Special Character: Double quotation " "

Purpose: To check for the exact phrase.

Example:

"apache tomcat" : Checks for values containing the exact phrase, such as apache tomcat, server apache tomcat is down, apache tomcat server is down, etc.
Phrases such as tomcat apache or apache licensed tomcat will not be validated.

Words Without Special Characters  

When you enter two or more words without using special characters ( " ", *, ? ), the system checks for values that contain the specified words in any order.

For example, apache tomcat matches apache tomcat, apache tomcat is down, tomcat apache, apache licensed tomcat, tomcat is apache, etc.

If the attribute value itself contains the special characters, prefix the characters with a backslash (). For example, if the value contains event*printer, enter the value as event*printer.