Sidekiq SLO Alert
Summary
Sidekiq SLO Alert
Timeline
All times UTC.
2020-04-05
- 05:01 - Incident declared from Slack
- 05:02 - Identifies it is
authorized_projects
onrealtime
fleet that is causing the issue - 05:06 - Co-relates to recent incidents for the same issue and finds epic that looks to resolve the issue
- 05:11 - Alert clears and incident is closed
Details
Sidekiq SLO alert.
Looks like due to sidekiq urgent - saturation on workers and node CPU utilization. Looking into it more.
Source
Incident declared by aamarsanaa 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)
Edited by Amarbayar Amarsanaa