Best Practices for Discovery Scheduling
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 03:05 AM
In creating a Discovery schedule, I would like to know the schedule division unit, IP addressing? I would like to know the best practices for the division range of the
In particular, if we have a segment for servers, I am assuming that the entire segment can be a single IP range, but I am wondering if we need to create separate IP ranges for different credentials....
While there may be unique local requirements, the discovery schedule is best organized based on the geographic location of the IP ranges to be discovered. I found this to be correct? Is it best practice to create one for each credential? Is this correct?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-18-2025 03:08 AM
Hi @SotaT
If my response proves useful, please indicate its helpfulness by selecting " Accept as Solution" and " Helpful." This action benefits both the community and me.
Regards
Dr. Atul G. - Learn N Grow Together
ServiceNow Techno - Functional Trainer
LinkedIn: https://www.linkedin.com/in/dratulgrover
YouTube: https://www.youtube.com/@LearnNGrowTogetherwithAtulG
Topmate: https://topmate.io/atul_grover_lng [ Connect for 1-1 Session]
****************************************************************************************************************
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-19-2025 07:00 AM
As per me and my real time project experience, I suggest below -
1. Always go with subnet mask which is Greater than /18 or /19 Max. Don’t go below /18 as it will impact so many places.
2. Always go with Location wise or region wise schedule if customer have really defined the IP ranges in such way. (I see in most of the cases customer did not define proper location segragration)
3. It’s better to go with protocol wise schedules like WMI, Or specific so that it execute the IP ranges only for that protocol for which it is defined instead of checking all protocol.
4. While scheduling the schedules always keep 15 mints gap between the schedules so that it won’t conflict.
this is my experience from real time project on ServiceNow ITOM Module.
✔️ If this solves your issue, please mark it as Correct.
✔️ If you found it helpful, please mark it as Helpful.
—
Shubham Jain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 02:48 AM
@SotaT was this helpful for you?
✔️ If this solves your issue, please mark it as Correct.
✔️ If you found it helpful, please mark it as Helpful.
—
Shubham Jain
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-21-2025 02:28 AM
-
Use separate schedules for Prod, Non-Prod, Network, Cloud, etc.
-
Run Discovery during off-peak hours.
-
Avoid overlapping IP ranges.
-
Break large IP ranges into smaller sub-ranges.
-
Assign correct MID Server using IP range or capabilities.
-
Use Credential Affinity to bind the right credentials.
-
Monitor Discovery logs and dashboards regularly.
-
Enable only required CI classifiers.
-
Review and update schedules periodically.
-
Test new schedules in a non-prod environment first.
✔️ If this solves your issue, please mark it as Correct.
