Populating Discovery data in a separate table?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2017 02:10 AM
Hi folks,
There is a requirement in which the client requires data from ServiceNow Discovery to populate a different table , say X, instead of cmdb_ci_*
There are Windows/Unix servers and Network devices in the environment, each of whose data from ServiceNow Discovery is required to populate tables other than the out of box tables for the respective classes.
Since the above is a strict requirement, how can I go about this, considering the feasibility of the activity?
Thanks in advance!
Supratik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2017 02:58 AM
Hi Supratik,
Why does your client want to move all the data's into a custom table? ServiceNow won't suggest this as a best practice.
In case, if they want to move it into a custom table then you need to look into this table discovery_classy.
Discovery device classification
Discovery classification decides in which table records needs to be created or updated.
Regards,
Vivek
Based upon the impact hit like, helpful or correct
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2017 04:01 AM
Thanks for the prompt reply Vivek.
The client is adamant on populating discovery data in a staging table, and then promote it to the golden data set (CMDB), despite this not being standard practice.
As suggested by you, I looked into the discovery_classy table. Would simply changing the corresponding table to the custom table (as shown below in screenshot) for each of the classifiers be enough to populate the custom table with the data for the respective classifier? Or will I have to modify probes/sensors as well?
Thanks,
Supratik

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-03-2017 04:15 AM
Yes, it should work but I never tried it personally. Don't create entirely a new table with custom field names, that will confuse the sensor to update the fields. Suppose for Windows classification extend your existing windows table so that all the field names will be same but still your sensors will work.
If your client is that much adamant you can ask ServiceNow to talk to your client saying it's not a best practice.
Regards,
Vivek
Based upon the impact hit like, helpful or correct