[{"data":1,"prerenderedAt":377},["ShallowReactive",2],{"docs-\u002Fdocs\u002Falerts":3},{"id":4,"title":5,"body":6,"description":369,"extension":370,"meta":371,"navigation":372,"path":373,"seo":374,"stem":375,"__hash__":376},"docs\u002Fdocs\u002F7.alerts.md","Alerts & notifications",{"type":7,"value":8,"toc":357},"minimark",[9,13,17,46,49,53,60,180,192,202,205,215,218,244,249,256,272,275,299,305,309,312,335,338,342,345,349],[10,11,5],"h1",{"id":12},"alerts-notifications",[14,15,16],"p",{},"When a monitor goes down (or recovers, or degrades), Vantaj can notify you through the channels you choose. Alerting has two parts:",[18,19,20,33],"ul",{},[21,22,23,27,28,32],"li",{},[24,25,26],"strong",{},"Notification channels"," — ",[29,30,31],"em",{},"where"," alerts are delivered (email, Slack, a webhook, and more)",[21,34,35,27,38,41,42,45],{},[24,36,37],{},"Alert policies",[29,39,40],{},"when"," and ",[29,43,44],{},"to whom"," alerts are sent, including escalation over time",[14,47,48],{},"You create channels once, then reference them from one or more policies.",[50,51,26],"h2",{"id":52},"notification-channels",[14,54,55,56,59],{},"A channel is a single delivery destination. Add and manage channels under ",[24,57,58],{},"Settings → Integrations",".",[61,62,63,76],"table",{},[64,65,66],"thead",{},[67,68,69,73],"tr",{},[70,71,72],"th",{},"Channel",[70,74,75],{},"What you provide",[77,78,79,90,100,110,120,130,140,150,160,170],"tbody",{},[67,80,81,87],{},[82,83,84],"td",{},[24,85,86],{},"Email",[82,88,89],{},"Any email address",[67,91,92,97],{},[82,93,94],{},[24,95,96],{},"Slack",[82,98,99],{},"An incoming webhook URL",[67,101,102,107],{},[82,103,104],{},[24,105,106],{},"Discord",[82,108,109],{},"A webhook URL",[67,111,112,117],{},[82,113,114],{},[24,115,116],{},"Microsoft Teams",[82,118,119],{},"An incoming webhook connector URL",[67,121,122,127],{},[82,123,124],{},[24,125,126],{},"Google Chat",[82,128,129],{},"A space webhook URL",[67,131,132,137],{},[82,133,134],{},[24,135,136],{},"Telegram",[82,138,139],{},"A bot token and chat ID",[67,141,142,147],{},[82,143,144],{},[24,145,146],{},"OpsGenie",[82,148,149],{},"An API key",[67,151,152,157],{},[82,153,154],{},[24,155,156],{},"Zapier",[82,158,159],{},"A webhook URL (trigger any Zap)",[67,161,162,167],{},[82,163,164],{},[24,165,166],{},"Linear",[82,168,169],{},"Connection details to open issues",[67,171,172,177],{},[82,173,174],{},[24,175,176],{},"Webhook",[82,178,179],{},"Any HTTPS URL — receives a JSON payload",[14,181,182,183,187,188,191],{},"Give each channel a name (e.g. ",[184,185,186],"code",{},"Engineering alerts",") so it's easy to pick later. After saving, use ",[24,189,190],{},"Send test"," to confirm it's wired up correctly before you rely on it.",[193,194,195],"blockquote",{},[14,196,197,198,201],{},"Email alerts can also go to ",[24,199,200],{},"workspace members"," directly — no channel setup needed. You pick members when building a policy (see below).",[50,203,37],{"id":204},"alert-policies",[14,206,207,208,211,212,59],{},"An ",[24,209,210],{},"alert policy"," decides what happens when a monitor it's attached to changes state. Create and edit policies under ",[24,213,214],{},"Incidents → Alert Policies",[14,216,217],{},"A policy has:",[18,219,220,226,232,238],{},[21,221,222,225],{},[24,223,224],{},"Name"," and an optional description",[21,227,228,231],{},[24,229,230],{},"Notify on recovery"," — also send a notification when the incident resolves (on by default)",[21,233,234,237],{},[24,235,236],{},"Alert on degraded"," — also trigger when a monitor enters the degraded state, not just when it goes fully down (on by default)",[21,239,240,243],{},[24,241,242],{},"An escalation flow"," — one or more steps that fire over time",[245,246,248],"h3",{"id":247},"escalation-steps","Escalation steps",[14,250,251,252,255],{},"Escalation starts the moment a monitor goes down. Each ",[24,253,254],{},"step"," has:",[18,257,258,265],{},[21,259,260,261,264],{},"A ",[24,262,263],{},"delay"," — how long to wait before this step fires (the first step is usually immediate)",[21,266,267,268,271],{},"One or more ",[24,269,270],{},"actions"," — each action sends to a channel or to specific workspace members",[14,273,274],{},"This lets you build a flow like:",[276,277,278,287,293],"ol",{},[21,279,280,283,284],{},[24,281,282],{},"Immediately"," → email the on-call engineer + post to Slack ",[184,285,286],{},"#alerts",[21,288,289,292],{},[24,290,291],{},"After 10 minutes"," (still down) → also notify the team lead via Telegram",[21,294,295,298],{},[24,296,297],{},"After 30 minutes"," → trigger OpsGenie",[14,300,301,302,304],{},"If the monitor recovers before a step's delay elapses, the remaining steps don't fire. With ",[24,303,230],{}," enabled, everyone who was alerted gets a recovery notification.",[50,306,308],{"id":307},"attaching-a-policy-to-a-monitor","Attaching a policy to a monitor",[14,310,311],{},"A policy only does something once it's attached to a monitor or heartbeat.",[276,313,314,321,328],{},[21,315,316,317,320],{},"Open a monitor and go to its ",[24,318,319],{},"Alerts"," tab",[21,322,323,324,327],{},"Click ",[24,325,326],{},"Attach policy"," and choose one",[21,329,330,331,334],{},"Use ",[24,332,333],{},"Manage policies"," to jump to the policy editor",[14,336,337],{},"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.",[50,339,341],{"id":340},"any-region-can-send-an-alert","Any region can send an alert",[14,343,344],{},"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.",[50,346,348],{"id":347},"domain-expiry-alerts","Domain expiry alerts",[14,350,351,352,59],{},"Domain expiry alerts use the same channels. Configure them per-domain rather than through a policy — see ",[353,354,356],"a",{"href":355},"\u002Fdocs\u002Fdomains-alerts","Expiry alerts",{"title":358,"searchDepth":359,"depth":359,"links":360},"",2,[361,362,366,367,368],{"id":52,"depth":359,"text":26},{"id":204,"depth":359,"text":37,"children":363},[364],{"id":247,"depth":365,"text":248},3,{"id":307,"depth":359,"text":308},{"id":340,"depth":359,"text":341},{"id":347,"depth":359,"text":348},"Get notified when something breaks — alert policies, escalation steps, and notification channels","md",{},true,"\u002Fdocs\u002Falerts",{"title":5,"description":369},"docs\u002F7.alerts","b39J4LnhqSVUwuq9TbJwH0IXiPIYW8P6z3vV2dc7bgc",1780583796958]