Best Practice for Triaging Large Volumes of Discovery Home Errors and Identifying Ownership

monishasp
Tera Contributor

Hi Everyone,

We are currently reviewing a large number of ServiceNow Discovery Home errors across the following categories:

  • Configuration
  • Internal
  • Credentials
  • Network
  • CMDB

Many of the error records only contain IP addresses, and we are finding it difficult to determine ownership and prioritize remediation efforts.

I would appreciate guidance on the following:

  1. What is the recommended approach for identifying the owning/support team when Discovery errors only show IP addresses?
  2. How do you determine whether an error is truly actionable versus expected?
  3. When a CI does not exist in CMDB, how do you correlate the IP address to an owner or support group?
  4. What is the best practice for excluding IPs or subnets that should not be discovered?
  5. Are there any standard reports or dashboards used to analyze large volumes of Discovery errors and identify recurring issues?

For reference, our current Discovery Home error counts are approximately:

  • Configuration: 41,000+
  • Internal: 29,000+
  • Credentials: 9,000+
  • Network: 2,400+
  • CMDB: 120+

How do other organizations prioritize these errors and reduce overall Discovery error volume over time?

Any best practices, reports, or processes would be greatly appreciated.

Thank you.

1 REPLY 1

AshishKM
Kilo Patron

Hi @AJ_TechTrek - Please suggest. 

 

Thanks,

AshishKM 


Please mark this response as correct and helpful if it helps you can mark more that one reply as accepted solution