On-call handover
By Toolspoke
Summarises the night's PagerDuty alerts in Slack so whoever takes the pager next starts informed.
Needs a Toolspoke account. You choose which project it installs into.
PagerDuty
Slack
Its last step
Post one message
- PagerDuty + Slack
- Required integrations
- Runs on a schedule
- Every day at 8am by default
- Post one message
- What its last step does
- Some actions can delete
- 2 of 23 actions in its tools
On this page
The short version
- What it is
- Summarises the night's PagerDuty alerts in Slack so whoever takes the pager next starts informed.
- Works with
- PagerDuty, Slack
- How often
- Every day at 8am, once you switch it on.
- What it never does
- Acknowledge, resolve, reassign, escalate or create an incident.
- What you need
- A Toolspoke account, with PagerDuty and Slack connected.
How it works
What each run does, from the "Each run" part of its own instructions.
- Step 1:
Fix the window the last 24 hours, or since the last handover post if that is longer.
- Step 2:
List incidents in the window with list_incidents, every status. For each one, read its log entries: when it triggered, who acknowledged, whether it was resolved by a person or by the monitor recovering on its own.
- Step 3:
Find who is on call now and next with list_oncalls, so the post can name them.
- Step 4:
Sort them
Still open: triggered or acknowledged and not resolved. These go first, each with how long it has been open and the last note on it. Resolved by a person: say what was done, from the notes. If there is no note, say that. Resolved on its own: group them by...
- Step 5:
Post one message to the channel chosen at install. Open with the count of open incidents and the name of the person taking over. If the night was quiet, say so in one line; a quiet handover is still a handover.
What you get
How the agent's own instructions describe what it hands back. Install it to see a real result.
Post one message to the channel chosen at install. Open with the count of open incidents and the name of the person taking over. If the night was quiet, say so in one line; a quiet handover is still a handover.
Integrations & requirements
On-call handover needs PagerDuty and Slack to work. You sign in to each one yourself.
PagerDuty
RequiredTriage incidents, acknowledge and resolve pages, and see who is on call.
Authentication: API key
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
Skills it follows
| Tool | Actions it offers |
|---|---|
| PagerDuty | 12 in all: 9 read, 1 write, 2 destructive. |
| Slack | 11 in all: 7 read, 4 write, 0 destructive. Nothing that deletes or permanently changes anything. |
A project can switch any action off, and every call is logged. The counts are what each tool offers; which of them the agent uses is up to its instructions.
What it will never do
- Acknowledge, resolve, reassign, escalate or create an incident.
- Add notes to incidents.
- Guess a cause that is not written in the incident or its notes.
If something goes wrong
If PagerDuty cannot be read, post that plainly and early, before 8am if you can. An on-call person who believes the handover is complete when it is not is worse off than one who knows it failed.
These are written into On-call handover's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
When it runs
On-call handover runs every day at 8am by default. Its routine arrives switched off. Turn it on when you are ready: every run costs your workspace money.
Install it into a project, or copy it to the builder and change its instructions, tools and skills.
Use On-call handover
Pick a project and connect the tools it needs.