Import Set and Import Logs

@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

@Swetham 

It depends on your use-case

@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.

@Ankur Bawiskar , Please advise.

Kind regards!

@Anurag Tripathi ,

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

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.

Thank you for this!  Spent 2 hours searching the internet trying to figure out why these logs weren't being created!

Hi @Ankur Bawiskar 

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.