Wolf Incident Postmortem
jefftk.com
Wolf Incident Postmortem
1–10 of 18 posts
Re: Wolf Incident Postmortem
#2Sensor was faulty, sensor replaced, system functioning normally.
Re: Wolf Incident Postmortem
#3This is awesome. Job well done, and hats off sir.
Re: Wolf Incident Postmortem
#4Cruel.
Re: Wolf Incident Postmortem
#5It took me longer than I care to admit to figure out this wasn't talking about a real incident. I figured flock was about some Kubernetes/VM thing.
Re: Wolf Incident Postmortem
#6Well done. Seems like a good prototype to show someone who is unfamiliar with how a postmortem should be written up.
Re: Wolf Incident Postmortem
#7It took me longer than I care to admit to figure out this wasn't talking about a real incident. I figured flock was about some Kubernetes/VM thing.
Context for those wondering: The Boy Who Cried Wolf
https://en.wikipedia.org/wiki/The_Boy_Who_Cried_Wolf#The_fab...
Re: Wolf Incident Postmortem
#8Reminds me of an admin story where each incident ended with updating /etc/motd
Re: Wolf Incident Postmortem
#9Here I thought Jeff K was a sly fox, not a wolf.
Re: Wolf Incident Postmortem
#10The only wolf evidence are alerts by a now-missing sentry saying "wolf" twice and "real wolf" once. Yet the conclusion due to missing sentry is 'wolf', and not only that, that there must have been only one wolf rather than a pack. If you don't have supporting evidence, this conclusion may be faulty, and the real fault may return.
My initial reaction is that there is no wolf. The sentinel began exhibiting a mental bug that reoccurred for 2 days until the sentinel broke and wandered off. I think the resolution should have an action item to continue closely monitoring sentinels for further bugs, and collect metrics to show proof of wolf. And, you know, maybe come up with an additional wolf countermeasure (if the fault was a wolf, it will probably come back)