Is there a way to exclude CI Classes from Discovery?

[Liz Brewster]

Is there a way to exclude CI Classes from Discovery?  Specifically, things like "Exit Interface Routing Rule" and "Next Hop Routing Rule"?  

[Ashish Chakrav1]

Hi Doug, Big Fan,  So for irrelevant CI classes, we are setting up a business rule to stop discovery. 
However I am torn on the a few classes (Disk & Memory Module and such) where these are attributes to the main Server CI, but exist in separate tables also. The CIs in their own tables look and read like garbage, but under the Server CI make sense. Could we stop the CI table from being populated, but still have them show up as attributes under the Server CI?

The reason I want to get rid of them, for 4000ish SErvers is have 35000 Disk CIs and 45000 Memory module CIs.

[doug_schulze]

So are they duplicates? if so you have different issues. You should'nt stop the creation of them if they are really records that exist. If they are 'right' and you just dont want to see them on the form then remove them from the view and they can sit happily in the background still providing value.

And they aren't necessary irrelevant as those records help populate the base class (computer) record with disk space and obviously memory values. These attributes would be important in tracking and trending even events. 

[VaranAwesomenow]

I know about the console, but I don't see where I can specify a specific CI Class.  I can't shut down all network discovery, but want to exclude specific classes within network:   "Exit Interface Routing Rule" and "Next Hop Routing Rule".  Are these "child" CIs to switches / routers?

We have implemented this cos it was creating too many CIs which are not relevant and same with relationships, as @doug.schulze mentioned it needs customization to OOB pattern, but bear in mind that during updates you need to manually update these patterns, there is a shared library that is used by multiple network patterns, in that shared library you need to remove the steps that does the discovery of the classes such as Exit Interface Routing Rule... along with relationships.

[Ashish Chakrav1]

Hi Anil, what did you finally do to stop the discovery of " Exit Interface Routing Rule" and "Next Hop Routing Rule"