Discovered item not matching the right CI
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-21-2022 09:41 AM
Hi,
When i click on the Reapply button, the discovered items are getting matched with the CI’s belonging to Unclassed Hardware class. There are CIs available with the same name belonging to the Window server class.
When ever I run the code for the FDQN rule using a background script, the right CI (CI belonging to Window server class is returned).
Can somebody help me with why this is happening/ how to resolve this?
TIA
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 04:48 AM
I wonder if the "Unclassed Hardware" CI is returned together with your "real" CI and the system just picks the first one it can find?
Perhaps excluding CI class "cmdb_ci_unclassed_hardware" from the query could help - or you turn it around and build a specific rule with higher priority that only searches the "cmdb_ci_win_server" class instead of "cmdb_ci"?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 09:38 AM
Hi,
Thank you for looking into this . I have added -(cmdb_ci_unclassed_hardware, sn_sec_cmn_unmatched_ci, cmdb_ci_incomplete_ip) to the System Property(sn_sec_cmn.ignoreCIClass)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-22-2022 09:42 AM
And when ever i run the code in the FQDN rule using a Background script, i match with the right CI. (CI not with the unclassed hardware class )
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-22-2023 06:42 PM
Hi, I was able to solve this by clearing the 'duplicate of' field on the ci.