How to enrich an alert with CMDB data after binding the CI?

[Fr_d_ric Dhuez]

Hi Guru!

I have a requirement from our business who wants enrich the alerts with CMDB data after the alert binds a CI.

For example, we would like to enrich the alert with the Support Group indicated into the CI impacted by this alert.

I didn't found how to do it from the Alert automation neither other kind of feature...

Is it possible to do it??

Thank you

Fred

[Steve50]

Fred,

You can use an alert management rule to populate Support Group on your Alert and if you are creating an Incident, you can do it there. There is an OOB subflow called Create Incident you can add to the Alert rule. You can add assignment group to the Create Task step and grab it from the Alert's CI. You can also update the alert in the step. It is not required to create a task at all.

There is also a system property you can set called evt_mgmt.alert_auto_assignment_field. See Alert assignment groups for teams. The docs do not say how they method works and the scripts/jobs for event management are usually not visible to developers/admins.

The first option will give you maximum flexibility and the ability to create incidents or tasks and set additional fields on both. The second options is faster to implement but you can only set the assignment group field and it might not work for larger implementations.

[Fr_d_ric Dhuez]

Hello Steve,

Thanks for your answer! Yes I already saw Alert Management rules but we have several rules to implement coming from BMC (we're in a migration process).

I believed that an other option was available but not...

I'll check the doc and play with OOB rules to see if it can match my requirements.

Thx

Fred

[Community Alums]

Hi @Frdric Dhuez ,

You can create a decision table according to the condition and add that decision table to subflow to populate the Assignment group.

[Fr_d_ric Dhuez]

Hello,

I have found partially my answer...we can change the fields more easily using SOW AIOps Alert Automation.

Using SOW AIOps by default you have a field mapping using Webhook integration, then using Enrich Automation you can change the fields for specific exceptions (there are several options).

In Xanadu the CI Identification part is still missing into SOW AIOps, but available from Yokohama.

Hope it helps.

Fred