[{"data":1,"prerenderedAt":272},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fmonitors":3},{"id":4,"title":5,"body":6,"description":264,"extension":265,"meta":266,"navigation":267,"path":268,"seo":269,"stem":270,"__hash__":271},"docs\u002Fdocs\u002F3.monitors.md","Monitors overview",{"type":7,"value":8,"toc":254},"minimark",[9,13,22,27,98,102,113,159,163,178,187,191,202,206,223,227,234,238,241,251],[10,11,5],"h1",{"id":12},"monitors-overview",[14,15,16,17,21],"p",{},"A ",[18,19,20],"strong",{},"monitor"," is a single check target. Vantaj runs it on a configurable schedule and records the result of every check.",[23,24,26],"h2",{"id":25},"status-values","Status values",[28,29,30,43],"table",{},[31,32,33],"thead",{},[34,35,36,40],"tr",{},[37,38,39],"th",{},"Status",[37,41,42],{},"Meaning",[44,45,46,58,68,78,88],"tbody",{},[34,47,48,55],{},[49,50,51],"td",{},[52,53,54],"code",{},"up",[49,56,57],{},"Check succeeded within the expected response time",[34,59,60,65],{},[49,61,62],{},[52,63,64],{},"degraded",[49,66,67],{},"Check succeeded but response was slow",[34,69,70,75],{},[49,71,72],{},[52,73,74],{},"down",[49,76,77],{},"Check failed — timeout, connection refused, or unexpected status code",[34,79,80,85],{},[49,81,82],{},[52,83,84],{},"paused",[49,86,87],{},"Monitor is manually paused and not being checked",[34,89,90,95],{},[49,91,92],{},[52,93,94],{},"unknown",[49,96,97],{},"Monitor was just created and has not been checked yet",[23,99,101],{"id":100},"check-interval","Check interval",[14,103,104,105,108,109,112],{},"Checks run at a fixed interval per monitor. Available intervals range from ",[18,106,107],{},"30 seconds"," to ",[18,110,111],{},"24 hours",": 30s, 1m, 3m, 5m, 10m, 30m, 1h, 6h, and 24h.",[28,114,115,125],{},[31,116,117],{},[34,118,119,122],{},[37,120,121],{},"Interval",[37,123,124],{},"Best for",[44,126,127,135,143,151],{},[34,128,129,132],{},[49,130,131],{},"30s – 1m",[49,133,134],{},"Critical services where downtime is costly",[34,136,137,140],{},[49,138,139],{},"3m – 5m",[49,141,142],{},"Standard production endpoints and high-volume APIs",[34,144,145,148],{},[49,146,147],{},"10m – 30m",[49,149,150],{},"Less critical or internal services",[34,152,153,156],{},[49,154,155],{},"1h – 24h",[49,157,158],{},"Background services, cron endpoints, low-churn checks",[23,160,162],{"id":161},"regions","Regions",[14,164,165,166,169,170,173,174,177],{},"Checks run from multiple regions — ",[18,167,168],{},"US East",", ",[18,171,172],{},"Europe",", and ",[18,175,176],{},"Asia Pacific",". A monitor's response-time chart breaks results down per region, so you can see where latency is coming from. Checking from more than one place also avoids false alarms caused by a single bad network path.",[14,179,180,181,186],{},"If your endpoints aren't publicly reachable, allowlist the checker IPs — see ",[182,183,185],"a",{"href":184},"\u002Fdocs\u002Fprobe-ips","Probe IPs & regions",".",[23,188,190],{"id":189},"alerts","Alerts",[14,192,193,194,196,197,201],{},"Opening a monitor's ",[18,195,190],{}," tab lets you attach an ",[182,198,200],{"href":199},"\u002Fdocs\u002Falerts","alert policy"," so you're notified when it goes down, degrades, or recovers. A monitor with no policy attached is still checked, but won't notify anyone.",[23,203,205],{"id":204},"grouping","Grouping",[14,207,208,209,212,213,169,216,169,219,222],{},"You can assign monitors to a ",[18,210,211],{},"group"," (e.g. ",[52,214,215],{},"Production",[52,217,218],{},"Staging",[52,220,221],{},"Third-party","). Groups are created on the fly — just type a name when creating or editing a monitor. Monitors with a group are displayed under a labelled section header in the list.",[23,224,226],{"id":225},"history-and-incidents","History and incidents",[14,228,229,230,233],{},"Every check result is stored. The ",[18,231,232],{},"History"," tab on a monitor's detail page shows a scrollable, filterable log of all checks. Incidents are opened automatically when a monitor goes down and resolved when it recovers.",[23,235,237],{"id":236},"uptime-calculation","Uptime calculation",[14,239,240],{},"Uptime % is calculated as:",[242,243,248],"pre",{"className":244,"code":246,"language":247},[245],"language-text","uptime = (up checks \u002F total checks) × 100\n","text",[52,249,246],{"__ignoreMap":250},"",[14,252,253],{},"It is always shown in the context of a selected timeframe (1h, 24h, 7d, 30d, 90d, or custom range).",{"title":250,"searchDepth":255,"depth":255,"links":256},2,[257,258,259,260,261,262,263],{"id":25,"depth":255,"text":26},{"id":100,"depth":255,"text":101},{"id":161,"depth":255,"text":162},{"id":189,"depth":255,"text":190},{"id":204,"depth":255,"text":205},{"id":225,"depth":255,"text":226},{"id":236,"depth":255,"text":237},"How monitors work, status values, intervals, grouping, and history","md",{},true,"\u002Fdocs\u002Fmonitors",{"title":5,"description":264},"docs\u002F3.monitors","RX8GTsXEWXH8AzZg-sncwV9A7lKicJAnv4vwHTj68qo",1780583796958]