Excluding Specific CIs from Discovery Updates Based on Defined Criteria

SayanH715925373
Tera Contributor

3 weeks ago

Hi everyone,
I am working on a pattern extension where I need to check if the SysObjectID matches a list of OIDs. If it matches, we need to exclude that CI from being updated by Discovery.

I am stuck at the second part, which is excluding the CI from updates. Can this be achieved through pattern steps?

Also, I came across something called an Identification Inclusion Rule—would that be helpful in this case?

0 Helpfuls
  • 768 Views
2 REPLIES 2

MushtaqMir
Tera Contributor

2 weeks ago

Hi Sayan ,

  1. Discovery is the preferred source for keeping CIs current, so excluding updates should be carefully considered.
  2. If you have another trusted source, you can manage updates using IRE rules.
  3. Patterns can check SysObjectID but don’t directly block updates — that’s handled by IRE logic.
  4. Identification Inclusion Rules can help control which sources update specific CI types.
  5. Please share more details about the device type, current issue, and expected outcome.

Regards

Mushtaq

0 Helpfuls

Sam Webb
ServiceNow Employee

2 weeks ago

You should not be amending patterns here. Instead, look at "Reconciliation Rules":

https://www.servicenow.com/docs/r/servicenow-platform/configuration-management-database-cmdb/r_Recon...

 

With them you are able to (via a user interface) declare which source is most authoritative for which type of CIs, down to an individual attribute level.

 

Some buyer beware on this though -

  • do not make changes to anything in 'identification' rules,
  • do not make changes to anything other than than the CI class(es) in scope for your challenge,
  • do not put this anywhere near Production until you've tested the living daylights out of it!

IRE has potential to cause big issues if/when you do it wrong. Keep changes small, well tested and based on observed behaviour not gut feel.

 

Hope that helps!

Sam

0 Helpfuls