ServiceNow Discovery is a powerful feature that helps organizations identify and manage their IT infrastructure. One of the most critical components for Discovery Administrators is the discovery_result table.
This table provides detailed insights into the outcomes of discovery schedules, enabling admins to visualize and optimize their discovery processes effectively.
What is the discovery_result Table?
The Discovery Result table stores the results of each discovery run. It acts as a summary dashboard for Discovery Admins, offering visibility into the performance and coverage of scheduled discoveries. Each record corresponds to a completed discovery schedule and includes essential metrics such as:
- Discovery Schedule: The name of the schedule executed.
- Discovery Status: Indicates whether the discovery was successful, failed, or partially completed.
- Started / Ended: Timestamps for when the discovery began and ended.
- Total IPs: The total number of IP addresses scanned during the schedule.
- Alive IPs: The number of IP addresses that responded during the scan.
- Active IPs / Active NC IPs: IPs that were active and network-connected.
- Dead IPs: IPs that did not respond.
- Duplicate IPs: IPs that appeared more than once in the scan.
- Created Devices / Updated Devices: Devices added or updated in the CMDB as a result of the discovery.
Why is this Table Important?
For Discovery Admins, the discovery_result table is more than just a log.
Here’s why:
-
Visibility into Coverage
By comparing Total IPs vs. Alive IPs, admins can determine how many IPs are actually reachable. A low ratio of alive IPs may indicate network segmentation issues or unnecessary IP ranges in the schedule. -
Schedule Optimization
If a discovery schedule consistently shows a high number of dead IPs, admins can refine the IP ranges to avoid scanning unused addresses, reducing unnecessary load and improving efficiency. -
Device Management
Metrics like Created Devices and Updated Devices help track CMDB growth and ensure accurate configuration data. -
Troubleshooting
Discovery failures or anomalies (e.g., too many duplicate IPs) can be quickly identified and addressed.
Best Practices for Using Discovery Result [discovery_result]
- Regular Review: Monitor discovery results after each run to identify trends.
- Analyze Alive vs. Dead IPs: Optimize IP ranges based on these metrics.
- Leverage Filters: Use filters like
Discovery Status = Endedto focus on completed runs. - Integrate with Reports: Create dashboards or scheduled reports for ongoing visibility.
#discovery #visibility
1 Comment
