- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on ‎07-14-2022 04:04 AM
I have realized that with San Diego, in the baseline configuration, import logs are not created when you import something using the transform maps.
In order to enable the import logs again, you have to create this property and set it to true:
glide.importlog.log_to_table
The complete documentation of the Import Set Properties is here:
https://docs.servicenow.com/bundle/sandiego-platform-administration/page/administer/import-sets/reference/r_ImportSetsProperties.html
- 2,673 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
@Ankur Bawiskar what do you recommend on this?? Is it the best practice to add this property "
glide.importlog.log_to_table" ?
Kind regards,
Swetha M
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
It depends on your use-case
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
@Ankur Bawiskar , Thanks for responding. We have an instance scan running and that has a finding that says "This tasks contain all findings pertaining to the check "Import Logs do not work unless you add property introduced in San Diego""
We are running in Utah , so wanted to check if it is a general best practice to have this property set.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
We have an instance scan running and that has a finding that says "This tasks contain all findings pertaining to the check "Import Logs do not work unless you add property introduced in San Diego""
We are running in Utah , so wanted to check if it is a general best practice to have this property set.
your advise on adding this "glide.importlog.log_to_table" property??
Kind Regards,
Swetha M
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi,
If you are doing this in a non prod instance I don't see any issue, but if you do this in prod there may be lot of new logs, as this will enable the info level logs too. Now writing in log is a DB write operation so it does slow your transaction too, more logs mean more processing time. Also in prod how often will someone check these logs.
Hope this helps.
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Thank you for this! Spent 2 hours searching the internet trying to figure out why these logs weren't being created!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
I wanted to let you know that in the baseline configuration of San Diego, import logs are not created when using transform maps. To enable the import logs, you need to create the property glide.importlog.log_to_table and set it to true.