Is is possible to have different IRE Rules for different Sources

Go to solution
Chris McDevitt
ServiceNow Employee
ServiceNow Employee

‎07-08-2022 07:48 AM

Experts,

Is possible to have Discovery Source A have a set of IRE Rules and Discovery Source B have its own set of IRE Rules?

There is a Tanium CMDB integration that sends its results to the IRE. The problem is that it is matching on Retired Assets, which that team does not want. Of course, we could prevent that, but the customer's ServiceNow Discovery team wants to match on Retired Assets so they do not create duplicates.  It does not appear as if we can fulfill both requirements. Thoughts?

0 Helpfuls
  • 986 Views
1 ACCEPTED SOLUTION

Go to solution
Not applicable

‎07-11-2022 08:17 AM

I am not aware of this being possible.  The IRE identification rules are defined so that it is source agnostic for identification.  It sounds like the business use case here is more along the lines of restricting updates.  Hypothetically even if you could do this via IRE identification rules, it would not find a match and create a duplicate CI which I am fairly certain is not the desired result.

To prevent updating a CI you could add a business rule to run before update that will filter to to retired assets and the discovery source of Tanium that would abort the transaction.

View solution in original post

5 REPLIES 5

Go to solution
Edward Hall
Tera Contributor

‎10-06-2022 11:45 AM

Begs the (rhetorical) question, why would discovery ever find a retired CI? If discovery can launch a probe or sensor on it, it should have a Configuration Item Status of - Installed

0 Helpfuls