Operate
Phone and text paging
When an app goes down, CLI texts the right people, then calls them, until someone says they're on it.
Slack messages are easy to miss at 3 am. Paging makes sure a real outage reaches a person.
When an app goes down (or a database fails over, or the project is put on hold), CLI texts the people you chose. Each text has an On it? link: tapping it tells CLI someone's handling it, so nobody else gets woken up. If nobody taps it in time, CLI moves to the next step, usually a phone call, then everyone on the project. When the app comes back, everyone who was paged gets a "back up" text.
How to do it: open a project, go to Settings, find Phone and text paging.
- Add your mobile number and type the code CLI texts you. Everyone who should be paged does the same (each person confirms their own number).
- Check the steps. The default is: a text to owners and admins straight away, a call after 10 minutes, then a call to everyone after 25.
- Turn on Page people when an app goes down, and press Send me a test text to see what it looks like.
An unanswered page also shows at the top of Needs you, with an I'm on it button.
Paging needs a Twilio account on the server: CLI_TWILIO_ACCOUNT_SID, CLI_TWILIO_AUTH_TOKEN and CLI_TWILIO_FROM (a Twilio number). Texts and calls go out through Twilio's Messages and Calls APIs. Calls read the alert twice.
Your number
POST /v1/me/pager-phone {"phone": "+14165550100"}
POST /v1/me/pager-phone/verify {"code": "123456"}
GET /v1/me/pager-phone
DELETE /v1/me/pager-phoneNumbers are E.164 (with the country code). The code lasts 10 minutes and allows 5 tries. Only confirmed numbers are paged.
The plan
PUT /v1/projects/:id/paging
{
"enabled": true,
"kinds": ["service_down", "database_failover", "project_on_hold"],
"steps": [
{"afterMinutes": 0, "people": "admins", "via": "sms"},
{"afterMinutes": 10, "people": "admins", "via": "call"},
{"afterMinutes": 25, "people": "everyone", "via": "call"}
]
}Owners and admins set it. people is admins (owners and admins), everyone, or a list of principals; via is sms, call or both. Up to four steps; the first is at minute 0 and each later step comes after the one before. Environments use their project's plan.
Pages
One page is open per problem (kind and app). Steps run on the minutely job until someone acknowledges: by the link in the text (GET /v1/pages/ack/:token, no sign-in, it only acknowledges) or POST /v1/pages/:id/ack. A service_up closes the app's page and texts everyone who was paged. Unclosed pages close after a day. Each project can send 40 texts and calls a day. GET /v1/projects/:id/pages lists recent pages with every send and its result; POST /v1/projects/:id/paging/test texts your own number.