Guides

A red check in the UI is not enough. Alert delivery must reach the right destination.

Notification channels attach to projects, and checks in the project inherit them. This keeps routing consistent when multiple jobs share the same operator or team.

Back to Guides Open Classic Docs Open AI API Guide

Notifications and Alerting

How channels attach to projects and how to validate that alerts are actually delivered.

When to use

Use this page when a user asks why they are not receiving alerts.
Use this page when setting up a project for the first time.
Use this page when deciding how to route failures to email or chat systems.

Inputs

A project containing one or more checks.
A configured notification channel such as email or Telegram.
A failure or timeout scenario to test end-to-end delivery.

Outputs

A project-level alert routing setup.
Verified notification delivery for real failures or timeouts.
Clear separation between monitor state and alert state.

Failure cases

The check goes down but no notification channel is attached to the project.
The channel exists but is not verified or is misconfigured.
Grace values are too short and create noise that users eventually ignore.

Copy-paste example

Notification validation checklist

1. Attach an email or Telegram channel to the project.
2. Stop sending pings for one check long enough to trigger a failure.
3. Confirm the UI state changes and a message is actually delivered.
4. Restore pings and confirm recovery behavior.

Getting Started The fastest path from account setup to a working heartbeat and alert. Use Cases and Playbooks Task-oriented guidance for cron jobs, backups, CI, imports, and background workers. Management API Authenticated API for creating, updating, pausing, resuming, and inspecting checks.

Current practical channels

Email is the lowest-friction default for small teams and individual operators.
Telegram is a good fit for immediate personal or small-team notifications.
Additional integrations are configured from the project integrations area in the UI.

Operational advice

Attach at least one email channel and one chat channel for critical projects.
Group related checks into projects to keep alert routing predictable.
Tune grace times carefully to reduce noise from late but otherwise healthy jobs.

AI guidance

When a user reports missing alerts, verify both check state and attached project channels.
Distinguish between a failing check and an undelivered notification.
Recommend a deliberate failure test whenever a new notification channel is added.