Alerts & notifications

When a monitor goes down (or recovers, or degrades), Vantaj can notify you through the channels you choose. Alerting has two parts:

• Notification channels — where alerts are delivered (email, Slack, a webhook, and more)
• Alert policies — when and to whom alerts are sent, including escalation over time

You create channels once, then reference them from one or more policies.

Notification channels

A channel is a single delivery destination. Add and manage channels under Settings → Integrations.

Give each channel a name (e.g. Engineering alerts) so it's easy to pick later. After saving, use Send test to confirm it's wired up correctly before you rely on it.

Email alerts can also go to workspace members directly — no channel setup needed. You pick members when building a policy (see below).

Alert policies

An alert policy decides what happens when a monitor it's attached to changes state. Create and edit policies under Incidents → Alert Policies.

A policy has:

• Name and an optional description
• Notify on recovery — also send a notification when the incident resolves (on by default)
• Alert on degraded — also trigger when a monitor enters the degraded state, not just when it goes fully down (on by default)
• An escalation flow — one or more steps that fire over time

Escalation steps

Escalation starts the moment a monitor goes down. Each step has:

• A delay — how long to wait before this step fires (the first step is usually immediate)
• One or more actions — each action sends to a channel or to specific workspace members

This lets you build a flow like:

1. Immediately → email the on-call engineer + post to Slack #alerts
2. After 10 minutes (still down) → also notify the team lead via Telegram
3. After 30 minutes → trigger OpsGenie

If the monitor recovers before a step's delay elapses, the remaining steps don't fire. With Notify on recovery enabled, everyone who was alerted gets a recovery notification.

Attaching a policy to a monitor

A policy only does something once it's attached to a monitor or heartbeat.

1. Open a monitor and go to its Alerts tab
2. Click Attach policy and choose one
3. Use Manage policies to jump to the policy editor

The same policy can be attached to many monitors, so you can define an on-call flow once and reuse it everywhere. Heartbeats are attached the same way from the heartbeat's detail page.

Any region can send an alert

Vantaj runs checks from multiple regions. Alert delivery is shared across them — whichever checker confirms the status change sends the alert, so you're never waiting on one specific region.

Domain expiry alerts

Domain expiry alerts use the same channels. Configure them per-domain rather than through a policy — see Expiry alerts.