on this page

Switching toolsComing from Grafana OnCall

Coming from Grafana OnCall

Grafana OnCall OSS was archived on 24 March 2026, and its phone, SMS and push delivery stopped the same day. A self-hosted OnCall can still run its schedules, but nothing reaches a phone. That last part is what Mast Pager does.

There's no OnCall importer and none is planned. You can export from a running OnCall instance through its API and rebuild by hand in the web app under On call, or as code with alert sources as code. The re-key checklist on the Opsgenie page applies to this move too.

Grafana's alerting doesn't need to change much. Its Opsgenie contact point works against Mast: set Alert API URL to https://mast.tissue.dev/opsgenie/v2/alerts and API key to a send key, and Grafana's resolves close the incident. The Grafana section has the details. A webhook contact point pointed at the send URL works too.

This page is the word list: what OnCall calls something, and what it's called here.


The words

Grafana OnCall Tissue Mast Notes
Integration Alert source Each integration becomes one alert source with its own send URL. The API calls it a channel
Alert group Incident One thing that went wrong, from the first alert to the recovery
Grouping of alerts into an alert group Dedupe and grouping Send a stable key and repeats count up on the open incident. Grouping collapses a flood on one alert source into one card with a count
Route (none) In OnCall a route is a rule that picks an escalation chain. Mast has no routes: make one alert source per chain and point each kind of alert at its own send URL
Timeline, alert group log Timeline Who was notified, on which device, and who acknowledged
Escalation chain Escalation policy Steps page a rotation, the next person on it, one person, everyone or another alert source
Schedule, rotation, layer Rotation Each layer becomes its own rotation
Override Override
Personal notification rules Devices Mast pages a linked phone or watch through push, and calls from a step with Call ticked. There are no per-person rules and no SMS
Maintenance mode Maintenance window
Important and default notifications Level: page, loud, normal, quiet Close, not the same. Mast has four levels, and the level a phone rings at is set by the send and capped by the alert source. Alert sources and levels
Acknowledge, resolve, silence Acknowledge, resolve, mute Mute silences one alert source for a while. A page still rings
(none) Vital (heartbeat) OnCall had a heartbeat on each integration. Here it's its own thing, a URL a job beats on a schedule

Where it isn't a match

New alert sources top out at loud. One made in the web app or from the command line can't page until someone raises its highest level from a phone. Do that for the ones that should wake people, then send a test page to check.

Slack as the place you act. OnCall let you acknowledge from Slack. Mast can post every event to Slack through a destination, but you acknowledge from the phone, the watch or the web app.