Discovery populating CI's with empty names

[Nishant16]

For certain classes in Servicenow CMDB we have CI’s with name showing as empty. How to fix this in discovery of these CI’s

For certain classes such as Switchport and other classes in cmdb we have a huge amount of CI’s created daily with empty name from discovery. For these classes do we need to create or update any sensors or probes in order to populate this data? What are the recommendations?

Do we need to be collecting data for these classes with discovery or do we have options to disable discovery for certain classes? 

[CMDB Whisperer]

The actual reality is that some CIs don't have names, because they are identified via other attributes or relationships, and determining a name to represent that data.  On the other hand, these CIs aren't truly managed as CIs and you don't typically need to be worried about the lack of a name, as long as you are using reference qualifiers, principal classes, etc. to make sure that users are only interacting with the CIs that you care about from an ITSM perspective.  Set your principal CI classes to classes in the Hardware, Service, Application, and Business Application spaces for example, and use the reference qualifiers to make sure that those are the only CIs that are displayed.  Name won't matter anymore for things like Switchports.

That said, it wouldn't be a bad idea if there were a separate display name field for CIs so that each class could independently determine its display value whether or not the name field is applicable for that class.  But there isn't one today.

[Nishant16]

@CMDB Whisperer Thank you for your response. I am wondering still if there's a way i can exclude the classes such as Switchport, next hop routing rule from the Discovery since i cannot do it from the Discovery configuration console.