Hello ITOM Admins and Developers,
Working in IT Operations often means juggling discovery, CMDB, and integrations while keeping discovery patterns, MID Servers, and data consistency under control. Here are some practical tips and tricks that can save you time and help avoid common pitfalls.
- Change Scope to Revert a Pattern
When you make customizations to a pattern and want to revert it back to the out-of-the-box version, you need to switch your scope to the patternβs application scope. Only then does the Revert to This Pattern UI Action become available.
- CI Classification on Custom Pattern : Select Identification in the Phase field.
While building custom discovery patterns, ensure the CI classification trigger probes phase is set to Identification rather than Exploration. Otherwise, the custom pattern will not be triggered.
- Sync Patterns After MID Server Upgrade or Reboot
Always remember to re-sync patterns to the MID Servers after theyβre rebooted or upgraded. This ensures the updated pattern logic is available during discovery runs.
- Unique MID Server Usernames
Each MID Server should have its own unique username. Sharing accounts between multiple MID Servers can cause confusion while troubleshooting errors in the discovery logs.
Example:
- MID_Test_01_AMS
- MID_Test_01_APAC
- Quickly Find Which Discovery Schedule a CI Belongs To
To quickly identify which discovery, schedule a CI belongs to (without manually checking IP ranges):
- Navigate to the CI record.
- Scroll to the Related Links section at the bottom.
- Click Discover Now or Show Discovery Events.
This performs a quick discovery and also shows the associated schedule name in the discovery_device_history table.
π‘ If you found this article helpful, please mark it as βHelpfulβ and feel free to share your thoughts or additional tips in the comments.
Regards,
Srinija Amisthapur
Rising Star 2025 β
Certified Technical Architect
