The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Santosh_Ksagar
Mega Sage
Mega Sage

ServiceNow Discovery is a powerful tool that automates the process of identifying and populating configuration items (CIs) in your CMDB. Rather than simply reading documentation, you’ll gain a deeper understanding by researching and answering practical, real-world questions.

How to Use This Article:

  1. Read each question carefully. Consider how ServiceNow Discovery works, review official docs, and examine your instance if available.

  2. Investigate and document your findings. Use logs, dashboards, and community best practices to build your answers.

  3. Share your insights. Post your answers and learning on the ServiceNow Community to help peers and validate your approach.

 

Core Discovery Operations

  1. In a large enterprise with segmented networks, how can we optimise MID Server placement and manage secure communication between MID Servers and the Discovery process?

  2. How can we troubleshoot credential failures when we know the credentials are valid, but Discovery fails authentication?

  3. What are the signs that we need a custom pattern instead of relying on out-of-the-box (OOB) patterns?

  4. How can we monitor and optimise Discovery schedules to avoid overlapping runs or overloading MID Servers?

  5. What’s your step-by-step approach when troubleshooting Discovery failures for specific CI types, such as network devices or server CIs?

  6. What’s the industry practice for ensuring Discovery processes comply with internal security and audit policies?

  7. How does Discovery interact with Event Management and Service Mapping, and what pitfalls should we watch for in integrated environments?

  8. How do we validate the accuracy of CI attributes populated by Discovery?

  9. How can we leverage the ECC Queue and probe/pattern logs for better debugging?

  10. In a hybrid cloud/on-prem setup, how can we fine-tune Identification and Reconciliation rules to prevent duplicate CIs when IPs or hostnames change frequently?

  11. What are the best practices for discovering devices that don’t respond to SNMP or WMI, especially edge devices or legacy systems?

  12. How do we handle unidentified devices discovered through IP sweeps but not classified or fully identified?

  13. How do we monitor and proactively manage ECC Queue congestion or MID Server resource exhaustion during large discoveries?

  14. How do we build custom Discovery patterns for internally developed applications or niche technologies not covered by OOB?

  15. Is there a best practice for tracking what changes Discovery makes to CIs, for audit or rollback purposes?

  16. How do we ensure that Discovery data supports accurate Service Mapping, especially when CI relationships are unclear or incomplete?

  17. Which logs and tools do you prioritise: ECC Queue, probe/pattern logs, MID Server logs, and in what order?

  18. In your experience, what’s the most common mistake teams make with Discovery in large hybrid environments, and how would you avoid it?

  19. In real environments, how do we manage multiple MID Servers across different regions or domains to ensure optimal load balancing and failover?

  20. What’s the best way to use the Discovery Dashboard to monitor discovery failures over time and correlate them with CI types or subnets?

  21. Can schedules be prioritised or run in parallel without overwhelming the MID Server or ECC Queue?

  22. In what scenarios would you define multiple behaviours for a single schedule, for example, Windows and SNMP in the same IP range?

  23. How do we validate if Shazzam launched the correct probes based on the behaviour configuration?

  24. Can you explain how discovery data impacts CMDB Health sub-metrics like completeness and correctness?

  25. How to work with multiple data sources like Discovery, SCCM, Azure, Import Set, JAMF, etc.?

  26. What is the difference between credential-based and credential-less discovery in ServiceNow, and in which scenarios should each be used?

  27. What is credential affinity in ServiceNow Discovery, and how does it improve the efficiency or accuracy of credential selection?

  28. What are the best practices for ServiceNow Discovery?


Advanced and Modern Scenarios

  1. How does ServiceNow Discovery handle virtualised environments like VMware, Hyper-V, and cloud-native services (e.g., AWS EC2 or Azure VMs)? What are the nuances of each?

  2. What is the role of the Shazzam probe in the horizontal discovery phase, and how can we verify that it’s functioning correctly?

  3. How do Discovery Patterns differ from legacy probes/scripts, and when should you use one over the other?

  4. What’s the significance of the Classification and Identification phases in the Discovery process, and how do they impact CI creation?

  5. How can we configure Discovery to respect maintenance windows or blackout periods in critical systems?

  6. What role does the IP Address Table play in managing Discovery data, and how should it be maintained to prevent pollution or misidentification?

  7. How does ServiceNow Discovery manage dependency mapping in environments with load balancers, NAT, or IP masquerading?

  8. What’s the difference between Horizontal Discovery and Top-Down Discovery, and when would you use each?

  9. How can Discovery be extended to collect custom attributes or metrics not available in the base pattern?

  10. How do Discovery errors and failures reflect in the CMDB Health dashboard, and how should they be remediated?

  11. What’s the difference between a Discovery Pattern and a Parse Variable, and how are they used in tandem?

  12. How can Discovery be used to track lifecycle status of assets, such as retired or decommissioned, and clean stale CIs?

  13. How does ServiceNow Discovery perform with IPv6 networks, and what adjustments are needed to support IPv6-only subnets?

  14. How can we integrate Discovery with Change Management or Incident Management to automatically trigger discovery after certain events?

  15. How do we scale Discovery for fast-changing environments like Kubernetes, serverless apps, or ephemeral workloads?

 

Next Steps:

  • Post your researched answers in the comments to share and compare approaches.

  • Vote on responses you find most valuable to help the community surface best practices.

  • Bookmark this article to return as you progress in mastering Discovery.