[{"data":1,"prerenderedAt":82},["ShallowReactive",2],{"term-i\u002Fincident":3,"related-i\u002Fincident":62},{"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":56,"sitemap":57,"stem":60,"subcategory":6,"__hash__":61},"terms\u002Fterms\u002Fi\u002Fincident.md","Incident",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",{},"An incident is when something has gone wrong in production and users are affected. It's not just a bug in your code — it's an active emergency with real users unable to use your product right now. Incidents have severity levels (P1 = everything's on fire, P4 = slight weirdness), and teams have processes for handling them fast.",[11,20,22],{"id":21},"real-talk","Real Talk",[16,24,25],{},"An incident is an unplanned interruption or degradation of a service that affects users. Incidents are classified by severity (P1\u002FSEV1 through P4\u002FSEV4), trigger an on-call response process, are tracked in incident management tools (PagerDuty, OpsGenie), and result in a postmortem once resolved.",[11,27,29],{"id":28},"when-youll-hear-this","When You'll Hear This",[16,31,32],{},"\"Declare an incident — checkout is down for all EU users.\" \u002F \"How many P1 incidents did we have last quarter?\"",{"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","An incident is when something has gone wrong in production and users are affected.","beginner","md","i",{},true,"\u002Fterms\u002Fi\u002Fincident",[49,50,51,52,53,54,55],"Incident Response","Postmortem","On-call","Pager","Monitoring","Alerting","Rollback",{"title":5,"description":41},{"changefreq":58,"priority":59},"weekly",0.7,"terms\u002Fi\u002Fincident","TwpaxftRzM5VpWemfPNCeECx45nUJ60hxPd1Ketjcl8",[63,66,70,73,76,79],{"title":54,"path":64,"acronym":6,"category":40,"difficulty":42,"description":65},"\u002Fterms\u002Fa\u002Falerting","Alerting is the part of monitoring that actually wakes people up when something goes wrong.",{"title":49,"path":67,"acronym":6,"category":40,"difficulty":68,"description":69},"\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":53,"path":71,"acronym":6,"category":40,"difficulty":42,"description":72},"\u002Fterms\u002Fm\u002Fmonitoring","Monitoring is keeping a constant eye on your app while it runs — tracking whether it's up, how fast it responds, how many errors it throws, and how much me...",{"title":51,"path":74,"acronym":6,"category":40,"difficulty":42,"description":75},"\u002Fterms\u002Fo\u002Fon-call","On-call means it's your turn to be the person who gets woken up at 3am if production breaks.",{"title":52,"path":77,"acronym":6,"category":40,"difficulty":42,"description":78},"\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":50,"path":80,"acronym":6,"category":40,"difficulty":68,"description":81},"\u002Fterms\u002Fp\u002Fpostmortem","A Postmortem is the meeting you have after an incident to figure out what went wrong and how to prevent it from happening again.",1776518288525]