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