Hi dear community, I'm currently helping on an impact analysis to activation of Log Separation [1] for a cloud infrastructure. We've noticed that DBCleaner on Steroids uses {Log_General} from PlatformLogs extension. What is the recommended approach to deal with this? Have you simply removed the reference and the logic to delete the logs or applied any toggles to keep most code dormant? Would be great to have a new component feature version supporting this, as well.
Thank you!
[1] https://success.outsystems.com/documentation/11/setup_outsystems_infrastructure_and_platform/setting_up_outsystems/keep_outsystems_log_data_in_a_separate_database/change_logs_storage_location_at_outsystems_cloud/
...I might have submitted this question too soon: just noticed that there is no need at all to remove the PlatformLogs extension or its tables since if you don’t update your apps, migrating from the old extension [PlatformLogs] to the new one [CentralizedPlatformLogs], you’ll stop seeing log records, as there won’t be any new records to fetch from the database. Believe it's also not a valid use case to have DBCleaner* delete logs from the CentralizedPlatformLogs anyway...
[2] https://success.outsystems.com/documentation/11/setup_outsystems_infrastructure_and_platform/setting_up_outsystems/keep_outsystems_log_data_in_a_separate_database/change_logs_storage_location_at_outsystems_cloud/#platformlogs-extension