AIOps

AIOps

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Cloud Pak for AIOps 4 tips: setting which alert fields map to topology

By Zane Bray posted Mon March 11, 2024 12:25 PM

  

When alerts flow into the Cloud Pak for AIOps, they will be associated with the topology, when configured to do so. The association is done by comparing certain key attributes in the alerts with defined matchTokens in the topology. If there is a match of any of these key alert attributes with a matchTokens item, the alert is associated with that topology resource.

On the topology side, matchTokens are selected topology resource attributes that are added to a special list specifically for the purpose of matching them to alerts. This list is called the matchTokens. If you inspect the "Details" of a resource, then select the "Show JSON" toggle, you will be able to see any, if they exist:

The topology resource attributes that are selected for the matchTokens list is done automatically by some of the off-the-shelf Observers. For any others, you will need to create a matchToken rule in the topology configuration, to specify which topology resource attributes should be added to the matchTokens list. Note that you will need to re-run the Observer job for the changes to take effect.
On the alerts side, by default the key alert attributes that are compared with the matchTokens items are the resource.sourceId and resource.name (in that order). But what if I want to change which alert attributes are used to compare to the matchTokens items?
Go to: Installed Operators > IBM Netcool Agile Service Manager > aiops-topology > YAML
Add the following lines to the place indicated below:
 helmValuesASM:
  aiopsAlert.entryPointFields: sourceId,name,myCustomField
This will modify the alert attributes used to resource.sourceId, then resource.name, then resource.myCustomField, in that order.
Note that the attributes specified must be sub-attributes of the resource attribute. To use custom attributes in the alert-to-topology mapping therefore, you could add them to the resource attribute as sub-attributes and then refer to them here. You only put the sub-attribute name however, not the full resource.* notation.
After you have made your changes to the aiops-topology instance configuration, remember to save your changes for them to take effect.
0 comments
44 views

Permalink