Meta tags:
description=incident content on DEV Community;
keywords=software development, engineering, incident;

Headings (most frequently used words):

the, incident, to, that, no, and, ended, how, ai, incidents, we, call, what, posts, dev, community, runbook, sent, me, dashboard, longer, exists, spare, never, came, back, well, can, small, local, model, classify, structured, logging, is, not, observability, first, 60, seconds, nobody, outside, room, knew, when, outage, every, was, severity, three, until, someone, important, noticed, restored, service, so, fast, destroyed, evidence, http, client, with, timeout, took, down, four, services, postmortem, names, person, has, already, failed, hacked, wordpress, two, attackers, hole, antivirus, saw, servicenow, management, tower, stack, light, integration, github, billing, wake, up, for, software, engineering, productivity, from, 00, am, panic, confidence, use, during, on, automation, automate, leave, humans, deadlock, production, trending, guides, resources,

Text of the page (most frequently used words):
#incident (32), the (30), shinder (18), follow (16), min (15), read (15), comment (15), comments (15), and (14), add (14), that (13), dev (12), serguey (12), sep (10), ended (6), how (6), incidents (6), sergey (6), software (5), call (5), sre (5), with (4), community (4), use (4), logging (4), observability (4), servicenow (4), wordpress (4), for (4), what (4), sergueyshinder (4), create (3), structured (3), not (3), first (3), seconds (3), nobody (3), outside (3), room (3), knew (3), when (3), outage (3), well (3), can (3), small (3), local (3), model (3), classify (3), from (3), panic (3), confidence (3), during (3), every (3), was (3), severity (3), three (3), until (3), someone (3), important (3), noticed (3), management (3), tower (3), stack (3), light (3), integration (3), runbook (3), sent (3), dashboard (3), longer (3), exists (3), postmortem (3), names (3), person (3), has (3), already (3), failed (3), restored (3), service (3), fast (3), destroyed (3), evidence (3), http (3), client (3), timeout (3), took (3), down (3), four (3), services (3), spare (3), never (3), came (3), back (3), hacked (3), two (3), attackers (3), hole (3), antivirus (3), saw (3), posts (3), production (3), nghề (3), không (3), nhiều (3), chẳng (3), sắc (3), automation (3), aug (3), samson (3), tanimawo (3), naveenkumar (3), namachivayam (3), billing (3), github (3), oleg (3), venkata (3), subramanya (3), vedagiri (3), reaction (3), odilon (3), hugonnot (3), itoperations (3), namz (3), menu (3), account (2), log (2), ability (2), sort (2), top (2), latest (2), relevant (2), sign (2), deadlock (2), automate (2), leave (2), humans (2), oncall (2), wake (2), engineering (2), productivity (2), reliability (2), sergeyshinder (2), search (2), place, where, coders, share, stay, date, grow, their, careers, made, love, 2016, 2026, ruby, rails, built, powers, other, inclusive, communities, open, source, forem, terms, privacy, policy, code, conduct, mlh, shop, contact, about, showcase, organization, accounts, advertise, help, education, tracks, videos, reading, list, challenges, home, space, discuss, keep, development, manage, your, career, trending, guides, resources, concurrency, deadlockproduction, jul, devops, learning, githubcopilot, alerts, forensics, security, itops, sysadmin, itsm, communication, tracing, triage, classifier, runbooks, oct, right, left, post, hide, close, powered, algolia, navigation, skip, content,

Text of the page (random words):
incident dev community skip to content navigation menu search powered by algolia search log in create account dev community close incident follow hide create post posts left menu sign in for the ability to sort posts by relevant latest or top right menu the runbook that sent me to a dashboard that no longer exists 晖莫 晖莫 晖莫 follow oct 4 the runbook that sent me to a dashboard that no longer exists runbooks oncall sre incident comments add comment 4 min read the incident ended and the spare never came back sergey shinder sergey shinder sergey shinder follow sep 24 the incident ended and the spare never came back sergeyshinder sre reliability incident comments add comment 2 min read how well can a small local model classify ai incidents namz namz namz follow sep 22 how well can a small local model classify ai incidents classifier incident triage ai comments add comment 5 min read structured logging is not observability the first 60 seconds 晖莫 晖莫 晖莫 follow sep 16 structured logging is not observability the first 60 seconds logging observability tracing incident comments add comment 4 min read nobody outside the room knew when the outage ended serguey shinder serguey shinder serguey shinder follow sep 11 nobody outside the room knew when the outage ended sergueyshinder itoperations incident communication 1 reaction comments add comment 2 min read every incident was a severity three until someone important noticed serguey shinder serguey shinder serguey shinder follow sep 10 every incident was a severity three until someone important noticed sergueyshinder itoperations incident itsm comments add comment 2 min read we restored service so fast we destroyed the evidence serguey shinder serguey shinder serguey shinder follow sep 9 we restored service so fast we destroyed the evidence sergueyshinder itoperations incident sysadmin comments add comment 2 min read the http client with no timeout that took down four services sergey shinder sergey shinder sergey shinder follow sep 8 the http client with no timeout that took down four services sergeyshinder sre reliability incident 1 reaction comments add comment 2 min read a postmortem that names a person has already failed serguey shinder serguey shinder serguey shinder follow sep 2 a postmortem that names a person has already failed sergueyshinder itops sre incident comments add comment 2 min read a hacked wordpress two attackers and the hole no antivirus saw odilon hugonnot odilon hugonnot odilon hugonnot follow aug 12 a hacked wordpress two attackers and the hole no antivirus saw wordpress security forensics incident 1 reaction comments add comment 22 min read servicenow incident management and tower stack light integration venkata subramanya sk vedagiri venkata subramanya sk vedagiri venkata subramanya sk vedagiri follow aug 10 servicenow incident management and tower stack light integration servicenow incident alerts comments add comment 5 min read github billing incident a wake up call for software engineering productivity oleg oleg oleg follow sep 12 github billing incident a wake up call for software engineering productivity github incident billing githubcopilot comments add comment 5 min read from 3 00 am panic to confidence how i use ai during on call incidents naveenkumar namachivayam naveenkumar namachivayam naveenkumar namachivayam follow sep 1 from 3 00 am panic to confidence how i use ai during on call incidents ai oncall incident learning comments 1 comment 11 min read incident automation what to automate what to leave to humans samson tanimawo samson tanimawo samson tanimawo follow aug 11 incident automation what to automate what to leave to humans sre devops automation incident comments add comment 2 min read incident deadlock production nghề không nhiều chẳng sắc nghề không nhiều chẳng sắc nghề không nhiều chẳng sắc follow jul 7 incident deadlock production production incident deadlockproduction concurrency comments add comment 15 min read sign in for the ability to sort posts by relevant latest or top trending guides resources a hacked wordpress two attackers and the hole no antivirus saw the incident ended and the spare never came back the http client with no timeout that took down four services we restored service so fast we destroyed the evidence a postmortem that names a person has already failed the runbook that sent me to a dashboard that no longer exists servicenow incident management and tower stack light integration every incident was a severity three until someone important noticed from 3 00 am panic to confidence how i use ai during on call incidents how well can a small local model classify ai incidents nobody outside the room knew when the outage ended structured logging is not observability the first 60 seconds dev community a space to discuss and keep up software development and manage your software career home dev challenges reading list dev videos dev education tracks dev help advertise on dev organization accounts dev showcase about contact dev shop mlh code of conduct privacy policy terms of use built on forem the open source software that powers dev and other inclusive communities made with love and ruby on rails dev community 2016 2026 we re a place where coders share stay up to date and grow their careers log in create account