Why does Discovery not use sys object source table like its intended to?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago - last edited 2 hours ago
Hi all,
We are running both agent based and agent less discovery and see that the ID field in sys_object_source table is either 'servicenow' or 'AgentClientCollector' as we see below
The issue we see is that when discovery runs again for the same CI, it will re run the IRE rules since it wont find a unique match for the CI in this table. Other integrations like Qualys populate unique ID field and this way the IRE does not get called all the time and ideally just once for a given CI.
Is this behavior of having a non unique value in the ID field out of box? It feels strange that ServiceNow's tool like Discovery itself doesn't make use of the sys_object_source functionality which can prevent performance overhead.
Thanks,
Ravish