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?

[Alberto Consonn]

Hi,

the standard way to exclude specific items from the Discovery is using the Discovery Configuration Console, it has to work.

What is your problem on it? Did you try to put something in the Exclude section or turn off some devices or applications?

The instance creates an update set record for any change you make to the console, could you check this?

If I have answered your question, please mark my response as correct and/or helpful so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.

Thank you

Cheers
Alberto

[Ashish Chakrav1]

The Discovery console does not offer any refinement in selection. I need Linux servers. I don't need their disks being mapped into a separate table. Network routers should be discovered but not their interfaces or routing rules. Hope that explains the query better.

[David A2]

What is the business case being presented to turn these off?

We had this same conversation within our organization because people saw running processes, disks and network adapters as 'muddying up' the CMDB an didn't see any value to that information. In the end, we decided that even though this information isn't valuable to us now, it could be valuable to us later and could allow us to utilize more orchestration and automation opportunities, whereas if we were to exclude those, we would probably forget it was a possibility in a year or two. It may seem like junk, but you may find it better to just adjust some filters so you're not wading through the data all the time, but it's still present and built onto the individual CI records.

Just my thoughts...

[Ashish Chakrav1]

i dont agree to this thought process, if i need them later , i should have the ability to enable them later. I dont need to have clutter in my Instance. The leaner the better.