IP Address and Location Fields Are Empty for Discovered CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello Community,
We have observed that several class CIs in our ServiceNow CMDB are being created or updated successfully, with the Discovery Source showing as ServiceNow and the Most Recent Discovery field populated. However, the IP Address and Location fields remain empty.
Could you please advise what could cause these fields to remain empty and how we can troubleshoot and resolve this issue? Are there any specific Discovery Attributes, identification rules, field mappings, or configurations we should check to ensure these fields are populated when applicable?
Thank you for your guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @vjanaga1 ,
First, check the Discovery Status and review the Discovery logs to identify which attributes are being updated in payload of discovery logs.
Next, verify the reconciliation rules for the ServiceNow data source to ensure the required attributes are allowed to be updated.
Also, check the Discovery Logs to identify which Discovery Pattern is running. Then, open the pattern and review each step to determine whether the IP Address and Location fields are being populated correctly.
Still unable to find then check if any data policy or Business Rules is running .
If this response has helped , Accept ✔️ the solution and mark helpful 👍
Regards,
Abhishek
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
I believe the IP address field on the CI record itself is a legacy field at this point. Are there any IP address records being created and associated with the discovered CI?
For the location information - how do you currently store location information on the discovered CI? Are you looking for a specific string in the name, a tag value of some kind, matching against an existing table, associating via location set to the discovery subnet, etc?