Need to stop creating additional CI'S (classes) From Discovery

Snow909
Tera Expert

Hello All,

 

I have a requirement where i want to exclude CI from creating  in CMDB when Discovery runs. As you know when discovery run on COmputer table, along with computer it will bring additonal 20 tables data( Disk, Network adapter,storage devices,DNS names, Disk Partition and so on..). All these are created when WMi patterns are triggered . I Dont want to get the disk partition CI to be created.  

For that i have created a IRE Data Source Rules on Disk Partition insert not allowed, when i run the discovery the on the ip address for that computer its getting failed at the patterns.  How do i exclude these classes whithout making any changes to the OOB. 

Snow909_0-1736451474550.png

 

if i delete the  disk partication CI and rerun the discovery  , its getting failed since i created a rule not to create CI.

Snow909_0-1736457835714.png

 

Helpful answers are appreciated. 

 

 

2 REPLIES 2

mdunwell
Tera Contributor

@Snow909 Hi, did you ever figure out a solution for this?

MattewW
Tera Contributor

I’ve run into this issue before most of the time it comes down to how the identification and reconciliation rules are set up. If Discovery can’t match an existing CI, it ends up creating a new one, sometimes in the wrong class. It helps to double-check your Discovery patterns and make sure they’re classifying correctly. Also, using reclassification rules and auditing your CMDB regularly can prevent this from happening too often. Hope that helps!