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)

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.

I really prefer when the "postmortem" label is metaphorical.

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

Reminds me of an admin story where each incident ended with updating /etc/motd

A very good observation: https://www.jefftk.com/p/wolf-incident-postmortem#1096589888...

This is awesome. Job well done, and hats off sir.

Well done. Seems like a good prototype to show someone who is unfamiliar with how a postmortem should be written up.

I remember Jeff K's old website: https://www.somethingawful.com/hosted/jeffk/

Sensor was faulty, sensor replaced, system functioning normally.

Here I thought Jeff K was a sly fox, not a wolf.

Cruel.