For 4D v19, we started a long-term refinement of our logs. Our first effort was to improve their format to give you better and clearer information. As for 4D v19 R3, we added 2 new functionalities: the ability to instantly pause logging and a way for support teams to easily help their customers configure their logs through a configuration file.
The first functionality is the ability to pause and resume logging. In the Maintenance tab of the server administration window, you now have a button called Pause logging. Clicking on it will interrupt all logging operations in 4D, waiting for you to click again to resume logging. The main use of this button is for performance: Logging takes resources, and if your server experiences a momentary slowdown, you can pause logging to help it handle the situation before activating it again. It can also be beneficial if you are running low on disk space and need time to find a solution to store your logs.
Pausing and resuming logging will also be available programmatically through a database parameter.
Log Configuration File
The second functionality is designed for support teams, yours as much as ours. We have often experienced human errors when it comes to log gathering, and as such, we decided to simplify the procedure. Support teams can now provide their customers with a configuration file: to activate it, the customer only needs to copy it in the proper directory or to load it through the maintenance page of a running server. All the proper logs will be activated with the proper options as long as the configuration file stays in the project settings. If you want more information on how to write such configuration files, I encourage you to read this page on our documentation website.
If you have any questions about these new features, don’t hesitate to ask them on the forum. We will gladly help you!