Could I change saving location of cronjob log including S3 domain?

[former_member628981]

We customized mediaModel's S3 long domain to short one through using defaultS3MediaURLStrategy several months ago.

long domain : https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com

short domain : https://media.domain.com

The short domain works well in storefront.

After a couple of months, Our AWS administrator removed public access authorities from S3.

So long domain doesn't work anymore.

Storefront's media url(short domain) still works well.

But we found a lot of cronjob errors in dynatrace.

Error logs showed old long S3 domain with cronjob log path as below.

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/h57/h... Rarely occurred

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/hed/h... Rarely occurred

https://blablabla-northeast-2-prod-metadata.s3-ap-northeast-2.amazonaws.com/sys-master/cronjob/hf9/h... Rarely occurred

I don't know why this error occurred.

Could I change saving location of cronjob log including S3 domain?

Even any little clue would be very helpful.

Thanks in advance 😃

[a_e_dubey]

Hi @hyunguk_kim,

I think this should be possible as for media we have folder path so may be for logs as well we should have some logic somewhere.

So probably juts debug the setter of log into CronJob Model and check this debug path where this logs are being saved and which path. Once you know the logic you can try to customize it. I have not done such thing only I am trying to give some thoghts.