[{"data":1,"prerenderedAt":82},["ShallowReactive",2],{"term-o\u002Fon-call":3,"related-o\u002Fon-call":61},{"id":4,"title":5,"acronym":6,"body":7,"category":40,"description":41,"difficulty":42,"extension":43,"letter":44,"meta":45,"navigation":46,"path":47,"related":48,"seo":55,"sitemap":56,"stem":59,"subcategory":6,"__hash__":60},"terms\u002Fterms\u002Fo\u002Fon-call.md","On-call",null,{"type":8,"value":9,"toc":33},"minimark",[10,15,19,23,26,30],[11,12,14],"h2",{"id":13},"eli5-the-vibe-check","ELI5 — The Vibe Check",[16,17,18],"p",{},"On-call means it's your turn to be the person who gets woken up at 3am if production breaks. Teams rotate on-call duty — one week you're it, next week someone else is. Being on-call is the reality check that makes engineers care about writing reliable software. Your pager doesn't care that it's Sunday.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"On-call is a rotation where team members are designated as the first responder for production incidents outside of business hours. On-call engineers carry a pager (or PagerDuty\u002FOpsGenie alerts) and are expected to acknowledge and begin addressing incidents within a defined SLA (often 5-15 minutes).",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"I'm on-call this week — please don't deploy anything major.\" \u002F \"Set up an on-call rotation in PagerDuty with fair scheduling.\"",{"title":34,"searchDepth":35,"depth":35,"links":36},"",2,[37,38,39],{"id":13,"depth":35,"text":14},{"id":21,"depth":35,"text":22},{"id":28,"depth":35,"text":29},"cicd","On-call means it's your turn to be the person who gets woken up at 3am if production breaks.","beginner","md","o",{},true,"\u002Fterms\u002Fo\u002Fon-call",[49,50,51,52,53,54],"Pager","Incident","Incident Response","Alerting","Runbook","SRE",{"title":5,"description":41},{"changefreq":57,"priority":58},"weekly",0.7,"terms\u002Fo\u002Fon-call","-sqo27X5u4qos0CrKjiKDZmD5fri8Ti7WWD5CHhMFEY",[62,65,68,72,75,78],{"title":52,"path":63,"acronym":6,"category":40,"difficulty":42,"description":64},"\u002Fterms\u002Fa\u002Falerting","Alerting is the part of monitoring that actually wakes people up when something goes wrong.",{"title":50,"path":66,"acronym":6,"category":40,"difficulty":42,"description":67},"\u002Fterms\u002Fi\u002Fincident","An incident is when something has gone wrong in production and users are affected.",{"title":51,"path":69,"acronym":6,"category":40,"difficulty":70,"description":71},"\u002Fterms\u002Fi\u002Fincident-response","intermediate","Incident Response is the process your team follows when production breaks. Who gets paged? Who's the incident commander?",{"title":49,"path":73,"acronym":6,"category":40,"difficulty":42,"description":74},"\u002Fterms\u002Fp\u002Fpager","A pager (or more likely PagerDuty\u002FOpsGenie today) is the alert that goes off on the on-call engineer's phone when something breaks in production.",{"title":53,"path":76,"acronym":6,"category":40,"difficulty":70,"description":77},"\u002Fterms\u002Fr\u002Frunbook","A Runbook is a step-by-step guide for handling a specific operational task or incident.",{"title":54,"path":79,"acronym":80,"category":40,"difficulty":70,"description":81},"\u002Fterms\u002Fs\u002Fsre","Site Reliability Engineering","SRE is Google's version of DevOps with a more engineering-focused twist.",1776518299137]