News for hackers. Stuff that matters.
Re:Wolf Incident Postmortem by h2odragon on Thursday January 19, 2023 @01:46PM (#34443924)
Sensor was faulty, sensor replaced, system functioning normally.
Re:Wolf Incident Postmortem by Communitivity on Thursday January 19, 2023 @02:00PM (#34444114)
This is awesome. Job well done, and hats off sir.
Re:Wolf Incident Postmortem by pixiemaster on Thursday January 19, 2023 @02:02PM (#34444141)
Cruel.
Re:Wolf Incident Postmortem by thebetatester on Thursday January 19, 2023 @02:19PM (#34444374)
It 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 by michaelnoguera on Thursday January 19, 2023 @02:33PM (#34444550)
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 by cialowicz on Thursday January 19, 2023 @02:22PM (#34444409)
Well done. Seems like a good prototype to show someone who is unfamiliar with how a postmortem should be written up.
Re:Wolf Incident Postmortem by paulgb on Thursday January 19, 2023 @03:10PM (#34444984)
Indeed. Bookmarked it for exactly this.
Re:Wolf Incident Postmortem by dvh on Thursday January 19, 2023 @02:39PM (#34444613)
Reminds me of an admin story where each incident ended with updating /etc/motd
Re:Wolf Incident Postmortem by msla on Thursday January 19, 2023 @02:41PM (#34444632)
Here I thought Jeff K was a sly fox, not a wolf.
Re:Wolf Incident Postmortem by 0xbadcafebee on Thursday January 19, 2023 @02:50PM (#34444738)
The 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)

Re:Wolf Incident Postmortem by abeppu on Thursday January 19, 2023 @02:55PM (#34444797)
I really prefer when the "postmortem" label is metaphorical.
Re:Wolf Incident Postmortem by barbazoo on Thursday January 19, 2023 @03:02PM (#34444884)
I don't get the joke but I browsed a bit, got to the story about "MA RMV Overloaded" [0] where they tried to renew their driver license. I was baffled by the fact that it was possible at all and even faster to renew your official driver license through a private company (AAA) than through their DMV office.

[0] https://www.jefftk.com/p/ma-rmv-overloaded

Re:Wolf Incident Postmortem by kayodelycaon on Thursday January 19, 2023 @03:12PM (#34445002)
Re:Wolf Incident Postmortem by mlyle on Thursday January 19, 2023 @03:13PM (#34445003)
It's about the "boy who cried wolf" vs how incident management works.

False positives can make real issues get an insufficient response when they occur (e.g. sentinel getting eaten).

Re:Wolf Incident Postmortem by jandrese on Thursday January 19, 2023 @03:44PM (#34445353)
False positives can be a far more serious issue than people are willing to admit. There are plenty of loss of life incident reports that include wording like "the operator disabled the alert system due to numerous false positives" near the beginning.

An example: https://www.youtube.com/watch?v=1zDcsjHyxr8

Re:Wolf Incident Postmortem by layer8 on Thursday January 19, 2023 @03:15PM (#34445020)
Re:Wolf Incident Postmortem by msla on Saturday January 21, 2023 @01:14AM (#34464320)
I remember Jeff K's old website: https://www.somethingawful.com/hosted/jeffk/