I noticed that on T187053: Setup puppet cron to delete old data daily the script we use to purge old afl_ip data from the abuse log to comply with the WMF privacy policy and the data retention policy broke in 2016 and it was not until today that we noticed that when we were working on making some of that data avalaible per T160357: Allow those with CheckUser right to access AbuseLog private information on WMF projects. This means WMF has been inadvertently collecting private data for more than 90 days. To avoid that in the future, please configure the purge_abusefilter and the purge_checkuser mediawiki cron jobs to email someone to let them know when the script has crashed, not run for some reason, etc. Please also expand this practice to any other maintenance script which could be tagged as 'critical' by its function. Thanks.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T285896: Ingest logs from scheduled maintenance scripts at WMF in Logstash
T187078: Re-consider ` >/dev/null 2>&1` as output of many cron'd MW maintenance scripts - Mentioned Here
- T160357: Allow those with CheckUser right to access AbuseLog private information on WMF projects
T187053: Setup puppet cron to delete old data daily
Event Timeline
Comment Actions
I agree with the general sentiment/idea, though implementation wise we should be going through icinga alerts or phab tasks and not emails.
Comment Actions
Im not sure if this is still valid however i have removed the puppet tag as this would be better done in the alertmanager repo now
Comment Actions
Understood, we will make a note of it in our backlog and carefully evaluate it when the opportunity arises