We got an alert at around 11:00UTC about the eventlogging_db_sanitization script not running on both db1107 and db1108:
Oct 16 11:00:00 db1107 systemd[1]: Started Apply Analytics data retetion policies to the Eventlogging database. Oct 16 11:00:00 db1107 eventlogging_cleaner[27817]: INFO: line 139: Executing command SELECT table_name, SUM(IF(column_name = 'timestamp', 1, 0)) AS has_timestamp_field, SUM(IF(column_name LIKE 'event_%', 1, 0)) AS event_field_count FROM information_schema. Oct 16 11:00:00 db1107 eventlogging_cleaner[27817]: ERROR: line 645: Some table prefixes in the whitelist do not match any table name retrieved from the database. Please review the following entries of the whitelist: ['ResourceTiming'] Oct 16 11:00:00 db1107 systemd[1]: eventlogging_db_sanitization.service: Main process exited, code=exited, status=1/FAILURE Oct 16 11:00:00 db1107 systemd[1]: eventlogging_db_sanitization.service: Unit entered failed state. Oct 16 11:00:00 db1107 systemd[1]: eventlogging_db_sanitization.service: Failed with result 'exit-code'.
root@db1107:/var/log/eventlogging_cleaner# systemctl list-units --state=failed UNIT LOAD ACTIVE SUB DESCRIPTION ● eventlogging_db_sanitization.service loaded failed failed Apply Analytics data retetion policies to the Eventlogging database LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 1 loaded units listed. Pass --all to see loaded but inactive units, too. To show all installed unit files use 'systemctl list-unit-files'.