Discovery Exclusion Best Practices

[danielbond]

Hello All,

I have been working with ServiceNow for about four weeks.   A lot of the CIs (94%) don't look like they have much value.   When I click on the below CIs the vast majority just look like stubs with empty information.   Is there a guide that explains how these CIs are useful to the various service now modules?   For instance I would think IP address would be an attribute of a CI not a stand alone CI.   Or is there a best practices document which discusses what items are typically excluded from being created as CIs?

Disk	68,639	3.79%
DNS Name	18,267	1.01%
Exit Interface Routing Rule	118,307	6.53%
IP Address	487,232	26.91%
Memory Module	28,549	1.58%
Network Adapter	72,826	4.02%
Next Hop Routing Rule	374,971	20.71%
Router Interface	218,419	12.06%
Switch Forwarding Rule	48,357	2.67%
Switch Partition	139,120	7.68%
Switchport	132,785	7.33%

Thanks,

Daniel

[BenPhillipsSNC]

Hi Daniel,

You might find this thread useful:

Need to stop midserver from creating certain CIs

Here is a Wiki article with some information about tweaking the Switching probe:

Data Collected by Discovery on Network Routers and Switches - ServiceNow Wiki

thanks

[Ankush13]

If I remember correctly, everything is treated as a CI in discovery. The above information you mentioned will be useful on case to case basis. What may not be required by you may be an important aspect for another customer. If something is not needed, you can simply disable the exploration SNMP query for the particular information that you dont need which will eventually prevent sensor from populating the details.