3 ms·
You don't have to go full on enterprise solution, but you could split your services into priorities of 1,2,3 etc depending how critical it is to the customers.
by democracy 4y ago
You don't have to go full on enterprise solution, but you could split your services into priorities of 1,2,3 etc depending how critical it is to the customers. Then say if its 1 (the highest priorty), have a process of involving A,B,C people (at the same time or escalating). Priority 1 takes full focus 24/7. Priority 2 takes office hours only, etc. We use pager-duty atm, but not sure about its pricing model. It works ok. Make people take turns on days/weeks so noone is burnt out and provide easy escalating with approachable people so noone is stressed about contacting someone else at night or over the weekend. Don't forget to pay people (or provide early log off/time in-lieu) for those who spend their time fixing/looking at issues.
edit: document you processes, keep updating, nothing worse than waking up at 3 am and having no clue who to contact or what to do ))
edit: update previous incidents/post-mortems
- Agaryan 4y agoOkay, thanks for your answer! So you're using pagerduty and defined your own incident process with priorities and roles. Interesting. When a crisis arises during the day, the whole team is meeting in a war room and focus on fixing it or only the on-duty people work on it?
- democracy 4y agoYeah, during business hours, its normally the team in charge takes ownership of the issue, the support person would just notify them and then follow up...