Incidents, without another tool.
When a monitor really fails, StatusTick opens an incident, alerts the right person, drafts the update for your users and records what happened. When it recovers, the incident resolves on its own.
- 14:05:08MonitorCheckout API down: 503 on 2 checks in a row.The incident starts at the first failed check.
- 14:05:09IncidentsIncident opened, severity High. Alert sent to Slack and email.Severity follows your rules for this monitor.
- 14:06:10StatusUpdate drafted for status.example.com.Waiting for a person to publish it.
- 14:07:41SamAcknowledged. Escalation stopped.From the link in the alert.
- 14:09:30SentryError rate on /checkout above 5%. Opened here too.Alerts from your other tools get the same steps.
- 14:12:02SamComment: rolled back the 14:01 deploy.Notes sit on the same timeline.
- 14:21:00MonitorCheckout answers 200 again. Resolved on its own after 16 minutes.After the good checks you set.
Checkout API is down
HighOpen · 16 minAssigned to Sam
503 on 2 checks in a row since 14:05 UTC. Stripe reports no incident.
- Step 1Slack and email to the on-call person.
- Step 2After 10 minutes, PagerDuty and the whole team.
- Step 3Up to 3 escalations, then it waits for a person.
- 14:05:09Slack #ops-alerts and sam@example.com
- 14:07:41Acknowledged by Sam. Step 2 never ran.
From failure to resolved.
Opens on its own
When a monitor stays down for the failed checks you set. Its start time is the first failed check.
Resolves on its own
After the good checks you set, with an optional delay against flapping.
Manual incidents
Declare one for problems no monitor can see.
Alerts from other tools
Grafana, Prometheus Alertmanager, Datadog, Sentry, CloudWatch or any JSON webhook open incidents too.
Severity rules
Critical, High, Medium or Low, per status, organization-wide or per monitor.
Work on it together.
Acknowledge and assign
Show who is on it. Acknowledging stops escalation.
On-call and escalation
Alert policies send each step to the channels and on-call people you choose, up to 3 escalations.
Timeline and comments
Status changes, alerts, escalations and notes in one place.
Roles and audit log
Owners, admins and members. Changes to monitors, channels and members are recorded.
Where alerts go.
Email
Verified addresses, a clear subject and one link to act.
Slack, Microsoft Teams, Discord
A webhook to the channel you choose.
Telegram
A private or group chat.
PagerDuty
Events API v2, for teams that already page through PagerDuty.
Webhooks
JSON to your endpoint, with bearer, basic or API-key authentication.
Checkout API is down
Down since 14:05 UTC: 503 on 2 checks in a row.
Checkout API has been down since 14:05 UTC: 503 on 2 checks in a row. Acknowledge with one link, and escalation stops.
Questions.
- Do I need a separate incident tool?
- For many small teams, no: incidents, acknowledge, on-call schedules and escalation are built in. PagerDuty stays an option.
- Can I open an incident by hand?
- Yes, for problems that no monitor can see.
- What does it cost?
- Nothing while in beta. Pricing comes with launch.
See it on your own product.
Point it at your product tonight. In the morning you’ll see what happened while you slept, and which of it needed you.