2020-05-01: postgres WAL-E is apparently delayed
Summary
2020-05-01: postgres WAL-E is apparently delayed
Timeline
All times UTC.
2020-05-02
- 13:15 - Incident declared from Slack
Details
An alert I haven't seen before fired: "last wal-e backup seen 20 mins ago": https://gitlab.pagerduty.com/incidents/PJWGBDR?utm_source=slack&utm_campaign=channel
I'm assuming it's referring to postgres archive_command invocations of wal-e, that continuously archives wal segments, rather than basebackups which we'd only expect to see once per day.
Source
Incident declared by cfurman in Slack via /incident declare
command.
Resources
- If the Situation Zoom room was utilised, recording will be automatically uploaded to Incident room Google Drive folder (private)