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"?  

[Michael de Boer]

Yes that is the idea.
So for example when you create an incident and need to select the CI, instead of showing all the CIs in the CMDB, it's possible to only show specific CIs.
And that can be CIs from specific CI classes or CIs that are assigned to the caller.

You can do this by chancing the "Reference qual" for the attribute, where you select the CI, in the dictionary.

Regards,

Michael

[VivekSattanatha]

Why do you want to exclude these classes from Discovery? It is better not to show these classes to end user where ever they see instead of disabling the discovery itself.

Regards,

Vivek

[doug_schulze]

You would want to modify the OOB pattern, and remove the collection of these pieces. Or better yet, duplicate the pattern then remove the library from yours so you continue to get updates.

Downside? You lose Layer2/3 relationships..so as Vivek mentions, better to just hide them to keep full functionality for it will be needed one day.

[Ashish Chakrav1]

Hi @doug.schulze could you do a walkthrough for modifying an OOB pattern for something like cmdb_ci_disk, the CI Class Disk. The CI details are already showing up in the Windows Server (cmdb_ci_win_server) CI attributes. This table essentially contains duplicated details.

[doug_schulze]

You could disable the entire storage library but then you would lose important relationships. If you have duplicates then you should clear those up and hide that table if no one is consuming it.