Default CI Binding not working as expected

[Bryan Graham]

Hi all,

All our event rules use the default CI Binding (ie. none have the Override default binding checked). However I'm finding around 10% aren't binding as expected. The node on the event record is being set correctly with either the fully qualified domain name or IP Address which matches with a configuration item, but no CI is set. The processing notes on the event report:

Binding alert CI process flow:
Node is FQDN
Node was not found, checking by name
Event CI type is empty
No CI found for binding (Failed to resolve the event node to CI id)

How do I troubleshoot this further? Is there any additional logging I can activate to try and see why some match and others don't?

Thanks,

Bryan

[robertgeen · Accepted solution]

Bryan,

Most of the time if you are using a hostname it should work correctly and when it doesn't it's always because of the difference in domain names on the FQDN. Is there any chance you can share and example CI that you think it should of matched along with a screenshot of an alert? Outside of that I don't know of any way to put it into debug mode unfortunately. You could put code in the post bind to do another lookup the way you think it should be done if the CI is blank.

[Bryan Graham]

Thanks Robert,

Have created a business rule to populate the CI if it's empty and no longer seeing any alerts without CI's, so working as expected.

cheers,

Bryan