Using Performance Analytics to create report of discovery sources
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi All,
We’re currently using multiple discovery sources, and as a result, some CIs are being discovered more than once. This makes it tricky to figure out which fields were updated by which source—especially when generating reports.
We’re considering using Performance Analytics to help identify:
- Which discovery source discovered a CI
- What fields were updated by each source
Has anyone tried something similar or have any ideas on how this could be done using Performance Analytics?
Appreciate any insights you can share.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Rather than capturing this in a report as a reactive approach, consider creating Reconciliation rules to handle it proactively and make sure only primary discovery source creates/updates the records in CMDB.
If there are supplementary information coming from other discovery sources, you can create the order accordingly so that it can update or amend the CI with additional information.
You can look at the option of using table cmdb_datasource_last_update to report on your requirements. Refer below article for more information
https://noderegister.service-now.com/kb?id=kb_article_view&sysparm_article=KB1893055
If this helped to answer your query, please mark it helpful & accept the solution.
Thanks,
Bhuvan