incident.io
An agent that watches a risky change pages you, and only you, through incident.io when it goes wrong.
How it works
- Agent watching your change
- Tripwire fires
- Your incident.io alert route
- Your phone rings
Workflows
Page you through incident.io
Off until you turn it onAn agent that watches a change you name pages you, and only you, through your own incident.io alert source when its tripwire fires, without paging the on-call rotation or declaring an incident.
Read before you turn it on
Anyone with the alert source token can page you, and each page shows in your organization's alert list.
What it costs
You need an incident.io On-call seat, and the rights to create one HTTP alert source and one alert route, or an admin who makes them for you.
Know before you turn it on
Anyone with the alert source token can page you, and each page shows in your organization's alert list. The alert route alone decides who is paged, so a changed route pages whoever it names.
Add incident.io to your Fleet
Paste this prompt into a T3 Code thread on a machine that runs Fleet.
Your install prompt
Add this Fleet pack to my setup with me: incident.io. Fleet already runs on this machine. Ask me each choice with your question tool, and run every command yourself. 1. Run `fleet update`, so this machine has the newest engine and packs. Then run `fleet packs`, and leave out each pack that is already on. 2. Read the setup note of each pack. Ask me what it asks, and collect the flags that it names. Where a note names "the setup command" or "the command in step 9", use the `fleet packs` command of this prompt. Do not run a step that a note puts after that command yet. - incident.io: ~/.local/share/fleet/engine/packs/incident-io/SETUP.md 3. Turn the packs on with one command, and add the flags that the notes name: fleet packs --add incident-io 4. Do the steps that each note puts after the command. 5. Run `fleet doctor`, and explain each line. Do each `To do:` line with me, and say what a sign-in is for before it opens. 6. My other machines take the change at their next `fleet update`. To give it to one now, run `fleet update` there.