Notification Settings

You can receive notifications when a monitor detects an incident or recovers.

Manako’s notification channels include two types: channels for alerting people (Email, Slack, Discord, LINE, Webhook) and channels for integrating events with external incident management and monitoring tools (PagerDuty, Datadog, GitHub, Grafana, Jira). Both types work through the same mechanism and are configured from the same screen.

How Notifications Work

When a monitor detects 5 consecutive downs, an incident is created and an alert is sent to the configured notification channels. When recovery is detected, the incident is automatically closed and a recovery notification is sent.

Notification Events

Event	Trigger Condition
Incident Created	When a monitor detects 5 consecutive downs and an incident is created
Incident Recovered	When a down monitor returns to normal and the incident is closed
Web Change Detected	When a web change monitor detects a page difference

Supported Channels

Email Just enter an email address. Simple notifications.

Slack Send notifications to a channel via Incoming Webhook.

Discord Send Embed messages via Webhook.

LINE Push notifications via Messaging API.

Webhook Send JSON to any HTTPS endpoint.

PagerDuty Integrate with incident management via Events API v2.

Datadog Send events to your dashboard via Events API.

GitHub Issues Automatically create and close Issues on incidents.

Grafana Display events on your dashboard via Annotations API.

Jira Automatically create and close tickets on incidents.

Plan Limits

Available Channels

Plan	Available Channels
Free	Email, Slack, Discord, Webhook (4 types)
Pro / Business	All 10 types (above + LINE, PagerDuty, Datadog, GitHub, Grafana, Jira)

Channel Limits

Plan	Max Channels
Free	5
Pro	15
Business	50

Notification Assignment

Notification destinations can be configured at two levels:

• Per monitor: Associate channels with a specific monitor (takes priority)
• Team-wide: Set as a default notification destination (fallback)

If a monitor has its own channels configured, those take priority. If not, the team-wide default notification destination is used.

Tip

We recommend setting up dedicated notification channels for critical monitors and leaving the rest to the team-wide default.

Flap Guard

When a monitor rapidly alternates between down and up states (flapping), the flap guard is automatically activated to prevent a flood of notifications.

Item	Value
Window	10 minutes
Threshold	3 times
Behavior	When more than 3 state changes occur within 10 minutes, notifications are temporarily suppressed
Release	Automatically released after the window (10 minutes) expires

Note

The flap guard only suppresses notifications. It does not affect monitor checks or incident recording. When KV is unavailable, the flap guard is automatically bypassed and notification delivery is prioritized.

Retries

If sending to all notification channels fails, automatic retries are attempted via Cloudflare Queues’ retry mechanism. If some channels succeeded, no retry is performed.

Troubleshooting

Notifications Not Arriving

1. Check that the notification channel is active: Verify that the channel appears in the “Notification Channels” list in the dashboard
2. Check monitor association: If using per-monitor notifications, verify that the channel is associated with the target monitor. If no association exists, the team-wide default notification destination is used
3. Check flap guard: If there are many state changes in a short period, notifications may be suppressed by the flap guard

Webhook Signature Verification Error

If the webhook signature doesn’t match, see the signature verification section in Webhook Notifications.