Sync Activity generating high data volume - log rotation is missing

[ICTRV]

The Sync Activity is creating a huge number of records.
Two days of testing with a few calendars by tow users primarily, has created more than 20K activity records.

We need a possibility to purge such records every week or make it as a setting parameter. Else we will possibly end up with a very heavy database.

[iscale-odoo]

Please tell us how do you wish to manage the rotation

[bvanjeelharia]

You need to provide a configuration option under configuration->settings wherein users can specify for how long the logs should be kept(in days).Keep the default as 7 days. Then the logs older than the number of days specified should be cleared from the system

[astirpe]

Adding log rotation is good but is not enough.

The logging mechanism should be fast and light, since it's invoked very often. But looking at the code of nextcloud_odoo_sync, the logging seems more complex than what is really necessary.

For example every time log_event() is invoked, some children records of model nc.sync.log.line are created, having a record of nc.sync.log as parent. So every time a log entry is written, multiple records are created in the database. Try to limit the logging records in database to one record per each log, for example by merging model nc.sync.log.line into nc.sync.log

When log_event() is invoked, other methods are also executed, like for example check_and_log_users(). This method does not only create multiple log lines but also it invokes search_read() and write() on model nc.sync.user, resulting in expensive usage of resources. Try to limit the logging mechanism to just doing the logging, without adding extra workload.

[astirpe]

In addition to my previous post, I would also say to remove nc.sync.error model and the 2 values defined in nc_sync_error_data.xml. Field error_code_id of type Many2one can be replaced with the 4 corresponding fields, eg. like: error_code, error_description, error_type, error_severity.