Unable to get rid of the Export file that discovery stores

[Mohammed Aamer Khan]

Hi Community,

I’m facing an issue where data is correctly retrieved from Discovery, but the import into Assets is taking an unusually long time. Upon investigation, I found that the "Application Service" object type is consuming most of the processing time during import.

To troubleshoot, I tried disabling the object type mapping for "Application Service" in the Discovery Import. However, this led to a new problem: the ZIP file generated by Discovery remains in the export location instead of being cleaned up. As a result, the next import process becomes even slower.

Has anyone encountered this before or have suggestions on how to resolve it?

Thanks in advance for your help!

Best regards,

[Marc - Devoteam]

HI @Mohammed Aamer Khan 

Can't you remove the file from the export location, this would be my first idea?

[Mohammed Aamer Khan]

Thanks for your response @Marc - Devoteam but removing file manually will not make sense. However, File is not storing anymore in the export location. 

[Marc - Devoteam]

HI @Mohammed Aamer Khan 

Remove the existing file manual, this is probably left, due to the fact you disabled the mapping.

Or see the logs, but it probably is related due to the mount of data and the resources that are available on your on-prem host.

Check CPU and Mem usage and see if you can configure your instance coumption.