Pages went off on Sun Feb 7 00:05:02 UTC 2021 because logrotate still has a job installed by the package (as well as the systemd service that the package installs), and when triggered by the schedule, it caused failure statuses in systemd.
Jan 17 00:00:02 clouddb1016 logrotate[6515]: Job for wmf-pt-kill.service failed because the control process exited with error code. Jan 17 00:00:02 clouddb1016 logrotate[6515]: See "systemctl status wmf-pt-kill.service" and "journalctl -xe" for details. Jan 17 00:00:02 clouddb1016 logrotate[6515]: error: error running shared postrotate script for '/var/log/wmf-pt-kill/wmf-pt-kill.log ' Jan 17 00:00:02 clouddb1016 systemd[1]: logrotate.service: Main process exited, code=exited, status=1/FAILURE Jan 17 00:00:02 clouddb1016 systemd[1]: logrotate.service: Failed with result 'exit-code'. Jan 17 00:00:02 clouddb1016 systemd[1]: Failed to start Rotate log files.
Get puppet to clean up the logrotate for wmf-pt-kill, add logrotate scripts for the multi-socket services, and perhaps mask the service that is installed by the package so it stops "failing" when things try to run it.