Skip to main content
Grafana OnCall OSS is no longer maintained. Squasher has no importer for it, so you recreate your schedules by hand and send Grafana alerts to Squasher, where they open incidents.

​
What moves and what does not

Squasher uses a schedule to show who is on call now. When AI triage fails on an issue or an incident, Squasher assigns it to that person.
Squasher sends incidents to channels, not to phones. If your team needs phone or SMS paging, keep a paging tool and send Squasher incidents to it with the PagerDuty destination.

​
Run both tools side by side

Keep Grafana OnCall paging while you set up Squasher. In Grafana Alerting, add a Squasher webhook to the contact point that sends to Grafana OnCall. Each alert then reaches both tools. See Grafana Alerting for the webhook URL and payload.

​
Recreate your schedules

1

List what you have

For each Grafana OnCall schedule, write down the members in order, the handoff day and time, and the time zone.
2

Create the schedule in the dashboard

  1. Select On-call in the sidebar, then select Create schedule.
  2. Enter a Name, select the Rotation members, and set the Timezone.
  3. Select Create.
The dashboard hands off every Monday at 09:00 in that time zone. It cannot edit a schedule after you create it.
3

Use another handoff time

To choose the day, the time, or the order of members, create the schedule with the Squasher CLI:
--handoff-day is 0 for Sunday through 6 for Saturday. List the members in rotation order. squasher on-call members --schedule <schedule-id> shows the user IDs in a schedule.
4

Add overrides

The CLI reads the project from SQUASHER_PROJECT_ID, or from --project.

​
Move alerts and on-call

  1. Connect Grafana Alerting. For other sources, see Inbound alert connectors.
  2. Recreate your routes as notification destinations and routes.
  3. If you need phone paging, add a PagerDuty destination and route your incidents to it.

​
Check parity

  • squasher on-call current names the same person as Grafana OnCall.
  • squasher on-call calendar --schedule <schedule-id> shows the same shifts for the next weeks.
  • A test alert from Grafana opens an incident in Squasher and reaches the right channel.
  • Every responder can sign in to Squasher.

​
Turn off Grafana OnCall

  1. Remove the Grafana OnCall integration from each contact point. Keep the Squasher webhook.
  2. Turn off the Grafana OnCall schedules after one week without missed alerts.

​
Next steps

On-call

Learn how rotations and handoff work.

Grafana Alerting

Open Squasher incidents from Grafana alerts.

Set up notifications

Route incidents to Slack, email, or PagerDuty.

CLI reference

Get the CLI and see every on-call command.