Guide lines for IRE configuration for multiple data source environment
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hello, I have been working with ServiceNow CMDB for a couple of years now, however, in my current role. This is the first time that our environment is set up with multiple discovery sources (SG-Intune, SG-SolarWinds, SG-SCCM, as well as Discovery). I am wondering if there are some sort of guidelines, playbook ,or suggestions on how exactly to implement an effective IRE. Currently, all the discovery sources seem to essentially be overwriting the CIs at the time of each discovery job and causing flapping/incorrect information depending on the current discovery source. For example, a device may be named one name in SolarWinds, but ServiceNow Discovery will have a different name.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
41m ago
Hi gagribben,
In your case, what you can do is set up reconciliation rules. Reconciliation rules set precedence/priority for which discovery source(s) should have the authority to update certain types of CI.
In your case, it seems like you don't want ServiceNow Discovery to update these devices. You can create a reconciliation rule for each source on your device class in CI Class Manager and have ServiceNow priority be last (or after the other SGC sources). You can fine tune it to only do this for certain attributes, or you can say you want this for all attributes. This is just an example of course and you will have to test out what will work for your environment.
When you set up reconciliation rules, you will have to rerun the authority SGC source so that it is updated with the correct values. Don't be surprised to see some errors or some things not working exactly as expected, since that could happen with changing your reconciliation rules. Be sure to keep an eye on your SGC and Discovery runs and tweak conditions/attributes accordingly.
You will also need to create data refresh rules along with the reconciliation rules. This is in case your SGC has not updated a CI in greater than X amount of days, another lower priority source can update it instead until the higher priority source updates it again. If you don't create a data refresh rule, it may work a bit wonky or it may not work at all.
