[{"data":1,"prerenderedAt":216},["ShallowReactive",2],{"docs-\u002Fdocs\u002Fmaintenance":3},{"id":4,"title":5,"body":6,"description":208,"extension":209,"meta":210,"navigation":211,"path":212,"seo":213,"stem":214,"__hash__":215},"docs\u002Fdocs\u002F8.maintenance.md","Maintenance windows",{"type":7,"value":8,"toc":200},"minimark",[9,13,26,33,38,51,54,58,114,118,178,185,189],[10,11,5],"h1",{"id":12},"maintenance-windows",[14,15,16,17,21,22,25],"p",{},"A maintenance window tells Vantaj that downtime during a known period is expected. While a window is active, the monitors you select are ",[18,19,20],"strong",{},"still checked",", but their status changes ",[18,23,24],{},"don't trigger alerts"," — so a planned deploy or database migration won't page your team.",[14,27,28,29,32],{},"Find it under ",[18,30,31],{},"Status → Maintenance",".",[34,35,37],"h2",{"id":36},"what-a-window-does","What a window does",[39,40,41,45,48],"ul",{},[42,43,44],"li",{},"Monitors keep running and their results are still recorded",[42,46,47],{},"Status-change notifications are suppressed for the selected monitors for the duration of the window",[42,49,50],{},"When the window ends, normal alerting resumes automatically",[14,52,53],{},"This keeps your uptime history honest while sparing you false alarms during planned work.",[34,55,57],{"id":56},"creating-a-window","Creating a window",[59,60,61,71,83,98,105,111],"ol",{},[42,62,63,64,67,68],{},"Go to ",[18,65,66],{},"Maintenance"," and click ",[18,69,70],{},"New maintenance window",[42,72,73,74,77,78,82],{},"Give it a ",[18,75,76],{},"title"," (e.g. ",[79,80,81],"code",{},"Database migration",") and an optional description",[42,84,85,86,89,90,93,94,97],{},"Set the ",[18,87,88],{},"start"," and ",[18,91,92],{},"end"," date\u002Ftime, and the ",[18,95,96],{},"timezone"," they're expressed in",[42,99,100,101,104],{},"Choose which ",[18,102,103],{},"monitors"," the window applies to",[42,106,107,108],{},"Optionally make it ",[18,109,110],{},"recurring",[42,112,113],{},"Save",[34,115,117],{"id":116},"one-time-vs-recurring","One-time vs recurring",[119,120,121,134],"table",{},[122,123,124],"thead",{},[125,126,127,131],"tr",{},[128,129,130],"th",{},"Type",[128,132,133],{},"Use it for",[135,136,137,148,158,168],"tbody",{},[125,138,139,145],{},[140,141,142],"td",{},[18,143,144],{},"One-time",[140,146,147],{},"A single planned event — a migration, a cutover, a one-off deploy",[125,149,150,155],{},[140,151,152],{},[18,153,154],{},"Daily",[140,156,157],{},"Routine nightly work, e.g. a backup window",[125,159,160,165],{},[140,161,162],{},[18,163,164],{},"Weekly",[140,166,167],{},"A regular weekly maintenance slot",[125,169,170,175],{},[140,171,172],{},[18,173,174],{},"Monthly",[140,176,177],{},"Monthly patching or billing-cycle jobs",[14,179,180,181,184],{},"For recurring windows you also set an ",[18,182,183],{},"until"," date so the schedule doesn't run forever. Each occurrence inherits the same duration and the same set of monitors.",[34,186,188],{"id":187},"tips","Tips",[39,190,191,194,197],{},[42,192,193],{},"Set windows a little wider than the work itself to absorb overruns",[42,195,196],{},"Scope the window to only the monitors affected by the work — unrelated monitors keep alerting normally",[42,198,199],{},"Times are stored in UTC internally but you enter them in the timezone you pick, so daylight-saving shifts are handled for you",{"title":201,"searchDepth":202,"depth":202,"links":203},"",2,[204,205,206,207],{"id":36,"depth":202,"text":37},{"id":56,"depth":202,"text":57},{"id":116,"depth":202,"text":117},{"id":187,"depth":202,"text":188},"Schedule planned maintenance so expected downtime doesn't trigger false alerts","md",{},true,"\u002Fdocs\u002Fmaintenance",{"title":5,"description":208},"docs\u002F8.maintenance","bMi_4iYVT772_XwR_vTrIE311y6MWYdRczZRoWngAR8",1780583796958]