Discovery Data Precedence rule

Nisha30
Kilo Sage

8 hours ago

Hello Experts,

 

We have discovered CI in environment 

Have multiple Data source - SCCM, Solarwinds , ServiceNow, Cloud etc..

 

'Discovery Source' was ServiceNow before we had another Data sources. Now since we have other SOurce they have updated the 'Discovery Source' as Solarwinds.

 

We created Data Precedence rule on CI classes. 

 

But after next schedule ran it did not updated the 'Discovery Source' Field = ServiceNow.

 

What has to be done to make it ServiceNow since 'ServiceNow' has been given the lowest order.

 

Thanks

0 Helpfuls
  • 151 Views
3 REPLIES 3

YashwanthV18760
Giga Guru

7 hours ago

Hello @Nisha30 

 

To update the 'Discovery Source' field to ServiceNow, even when it has the lowest data precedence, follow these steps:

  1. Update the system property glide.discovery.source_name to "ServiceNow".
  2. Modify the dictionary entry for the Configuration Item [cmdb_ci] table:
    • Navigate to the discovery_source field.
    • Update the choice list to include only "ServiceNow" (if required for consistency).
  3. Manually update existing records:
    • Open the Configuration Item [cmdb_ci] table.
    • Filter records based on the current Discovery Source value.
    • Use the Update All option to set the value to "ServiceNow".
  4. Update the Source [sys_object_source] table:
    • Filter relevant records.
    • Use Update All to set the name field to "ServiceNow".

Important Note:

  • Reconciliation rules cannot be configured for the Discovery Source field.
  • Updates from a lower-priority source (like ServiceNow in this case) will only be accepted:
    • If it is the first update, or
    • If the CI attribute is considered stale based on data refresh rules.
0 Helpfuls

BharatC
Kilo Guru

6 hours ago

Hello @Nisha30 

 

Hi @Nisha30 

 

The discovery_source field is a tracking field for the last successful reporter. To ensure "ServiceNow" remains the primary source, check these three things:

1) Re-Run Discovery: The field will not update retroactively. ServiceNow must run a successful scan after the precedence rules were created to "reclaim" the field from Solarwinds.

 

2)  Check Reconciliation Rules: Precedence rules only work if a Reconciliation Rule exists for that CI Class.

Go to CI Class Manager > [Your Class] > Reconciliation Rules.

Ensure ServiceNow is added as an authorized source for "All Attributes."

 

3) Check for "Discovery Source" Overrides: If you are using a Service Graph Connector for Solarwinds, it may be bypassing standard IRE logic. Ensure the Solarwinds Data Source is explicitly listed in the Data Source Precedence module with a higher order number (e.g., 200) than ServiceNow (e.g., 100).

 

Please mark this response as Helpful & Accept it as solution if it assisted you with your question.

Thanks

 

 

0 Helpfuls