I am preparing to enable log separation in our environments and as per Change logs storage location at OutSystems Cloud - OutSystems 11 Documentation the direct access to logs via the PlatformLogs extension will no longer be possible.
During my analysis of impacted modules, I've found that the FeatureToggle_Lib exposes some API's, /FeatureToggle_Lib/rest/FeatureToggleAPI/EV_FeatureToggle_GetErrors and /FeatureToggle_Lib/rest/FeatureToggleAPI/EV_FeatureToggle_GetHits that wrap around SQL queries that are implemented by the PlatformLogs extension. It's not easy for me to determine the impact of these API's not working. Can the development team possibly provide some feedback on the impact of these API's no longer returning records, and also indicate if there's any plans to develop a version of the FeatureToggle_Lib that implements the CentralizedPlatformLogs extension.
Thanks
The FeatureToggle component is not prepared yet to handle the separation of logs and use the CentralizedPlatformLogs extension for that scenario. However, by proceeding with the separation in your environment, you will not have breaking issues in the business applications which are making use of Feature Toggles.The "EV_FeatureToggle_GetErrors" and "EV_FeatureToggle_GetHits" APIs are being consumed by LifeTime to capture data from each environment and present it in the "Analytics" and "Missing Keys" features of the Feature Toggle Management Tool, so the only impact of proceeding with the logs separation would be losing new data for those features. It's also advisable to inactivate the timers Timer_FeatureToggleHits_Sync and Timer_FeatureToggleErrors_Sync from the module FeatureToggleManagement_CS deployed in LifeTime, in order to avoid exceptions being repeatedly logged in Service Center.