Bug #15073
closedAdd switch to disable some compliance and change tracking features for performance
Description
There is several features that we want to be able to tweak (if possible without restarting rudder) that have a big influence on loaded environement:
- changes. This is highly stressfull for database, and even if Rudder can not work without them, we would like to be able to disable changes to help analyse perf problems,
- dynamic group computation at the begining of generation (idem than for changes)
- wrtiing node compliance level: this can be stressfull and it is not used but if you have the reporting plugins
- writing node compliance: this one should be off by default, there is 0 reason to keep it in Rudder 5.0 as it's not used anymore, not even by the reporting plugin.
All of these feature will be properties that will be switchable via Settings
API, but they won't be exposed in the settings web page as they should not be changed.
The can be changed with:
# use 'false' or 'true' # compute dynamic group at start of policy generation curl -k -H "X-API-Token: xxx" -X POST 'https://.../rudder/api/latest/settings/rudder_generation_compute_dyngroups' -d "value=false" # compute "changes" (globaly) curl -k -H "X-API-Token: xxx" -X POST 'https://.../rudder/api/latest/settings/rudder_compute_changes' -d "value=false" # save compliance levels in database curl -k -H "X-API-Token: xxx" -X POST 'https://.../rudder/api/latest/settings/rudder_save_db_compliance_levels' -d "value=false" # save detailled compliance reports in database (should be set to false) curl -k -H "X-API-Token: xxx" -X POST 'https://.../rudder/api/latest/settings/rudder_save_db_compliance_details' -d "value=false"