FQDN Node value not mapping to Configuration Item

[Mike Moody]

I'm having an issue where I'm passing a server FQDN as the node field value into the em_event table records, and the value is not being mapped to the existing server CI.

Here is the message I'm seeing in the Processing Notes field of the em_event records:

Binding alert CI process flow:

Node is FQDN

Node was not found, checking by name

No CI found for binding (Failed to resolve the event node to CI id)

I find the above message interesting because it seems to imply that it recognizes the value is a FQDN, however is unable to match it to the existing CI.

I only have one CI which has the FQDN in question.

Any ideas on why the Configuration Item is not being successfully bound, or how to fix this? Thanks!

[Tony Branton]

Hi Michael,

There are a couple of things you can try, both involving an Event Rule.

Option 1: Use an Event Rule Transform to map the "node" field to the "fqdn" field:

This may be enough for Event Management to identify a CI to bind the alert to.

Option 2: If option 1 doesn't work, you need to set the "ci_identifier" using an Event Rule Transform to something like this:

Or you could just compose "name" using ${wkstation} since you're sending that in the event.   You can treat "ci_identifier" as a search key and use multiple CI fields to accurately match a CI in the CMDB.

Hope this helps.

[Mike Moody · Accepted solution]

Hi Tony,

Thanks for your advice. It turns out that my issue was actually related to the fact that I'm using a domain separated instance of ServiceNow and my Event's were not being created in the same domain as my configuration items. I've got it all sorted now. Thanks!