You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the log table contains many entries this slows down the backend panel and also every incoming request, since we insert every request to the log table. This occurs if we have ~20000 requests per day. We should start to fragment the log table so that the log table contains only requests for i.e. a month. Maybe we should also add an option how many logs we should keep or a way to complete disable logging.
The text was updated successfully, but these errors were encountered:
We have created a new command system:log_rotate which basically creates a new log archive table which copies all log data into this archive table and then truncates the log table. Through this a user could setup a cron which calls this command in arbitrary intervals.
If the log table contains many entries this slows down the backend panel and also every incoming request, since we insert every request to the log table. This occurs if we have ~20000 requests per day. We should start to fragment the log table so that the log table contains only requests for i.e. a month. Maybe we should also add an option how many logs we should keep or a way to complete disable logging.
The text was updated successfully, but these errors were encountered: