On-call in Maple: schedules, escalation, acknowledgements and silences
Page whoever is on call, escalate until someone acknowledges, and silence alerts during a deploy, without a separate paging tool.
Maple alerts now cover the whole path from a firing rule to the person who fixes it. Everything below is in the Alerts hub.
Acknowledge an incident
Click Acknowledge on an incident or in the inbox, or on the alert card in Slack or Discord, to tell your team you are on it. While an incident is acknowledged, reminders stop. If it gets worse and moves from warning to critical, it pages again. When the incident already paged PagerDuty, the acknowledgement is sent there too. The inbox lists unacknowledged incidents first, and the incident timeline records who acknowledged it and from where.
Escalation chains
A chain is a list of steps: notify these destinations or people, then wait a number of minutes for someone to acknowledge before the next step. For example, “post to #alerts, then page the on-call after 10 minutes, then the team lead”. A chain can repeat. Build chains on the Routing tab and attach one to a rule’s warning or critical tier. Acknowledging pauses the chain, and the incident page shows which step it is on and when the next page goes out.
On-call schedules
The new On-call tab holds your rotations. A schedule has a time zone and up to five layers, each rotating its people daily, weekly or every few hours, optionally only in some hours or days (weekends, or 22:00 to 06:00). An override covers a shift for someone else. Each schedule has a week calendar with the final rotation and its overrides, and the inbox shows who is on call now. An escalation step can page “whoever is on call” on a schedule, by email, Slack direct message or Discord direct message.
Silences
Silence alerts for a deploy or a planned migration without turning rules off. Silence one rule or one incident’s group for 1 hour, 4 hours, until 09:00 or a custom end, or create a silence on the Silences tab that matches rules by service, environment or tag. Rules keep evaluating while silenced. If an incident is still open when the silence ends, its page goes out then.
Maintenance windows are recurring silences, such as “every Sunday 02:00 to 04:00 in Europe/Berlin”, and keep planned downtime out of anomaly baselines. For now they are set up through the API and MCP; the dashboard comes next.
Anomalies route like alerts
Detected anomalies now page through alert rules, so they get destinations, warning and critical tiers, acknowledgement, silences and escalation like any other alert. Open anomalies are the Anomalies view of the inbox, and an anomaly rule can be scoped to services, environments and signals. Paging on anomalies stays off until you add a destination.
All of this is available from the API and the MCP server as well, so an agent can ask who is on call, acknowledge an incident or silence a noisy rule.