Turn off discovering specific classes / libraries of CIs from Discovery

[sgowtham1024]

Hi All,

I need to stop discovering running processes, network adapters and disks associated with computers while discovering. 

I tried creating a new behaviour but for windows, the horizontal probe runs the whole library to fetch installed software, running processes, etc into the CMDB.

I also used the discovery console to disable software/process identification but doesn't seem to work.

Any suggestions?

[David Herold]

Leaner CMDB is what we are hearing from Gartner but is there an easier way to turn off items such as noted above " Network routers should be discovered but not their interfaces or routing rules."  ?

[gwaddy100]

Hi guys, did anyone manage to get a definitive answer for the best approach to excluding discovery of certain CI classes? Like the examples above, I want to stop discovering tracked configuration files associated with windows servers. I can't switch windows servers off as a whole as these are required. I am also with the "the learner the better" school of thought. I only want thing that add value, making it easier to maintain CI lifecycle/quality of data for a smaller amount of CIs. Any advice on how to implement this would be appreciated. I have seen an approach on a separate thread advising to create an ACL to stop the mid.user from creating on that specific CI class table. Is this best practice or would anyone recommend an alternative? 

[Daniel Grande]

Hello I am wondering if anyone ever figured out how to stop discovering certain classes. Our issue is Network Adapters we have determined we do not need these and we have over 5 million network adapters. I am going to archive the adapters that have already been discovered but I would like to stop discovery on them all together. I have checked the Discovery Console but Network adapters are not an option to switch on and off.