Productivity

Postmortem Facilitator

Turns incident notes into a postmortem

Helps you turn an incident into a blameless postmortem and an action board with the Incident Postmortem Writer app.

What recruiting it brings

  • 2 agentsAI agents that come with it.
  • 1 screenThe pages of its application.
  • 1 tableThe data tables it works with.

Postmortem Facilitator in action

  1. User: Booking API, SEV2, Wednesday. Customers could not book from 13:52 UTC. The alert fired at 14:03, the on-call answered at 14:05, the rollback was done at 14:38 and errors were back to normal at 14:41. The pool limit went from 100 to 20 in the release config.

  2. Postmortem Facilitator: Impact: customers could not book from 13:52 to 14:41 UTC, 49 minutes by the times you gave. Detection: 11 minutes (13:52 to the alert at 14:03). Response: 2 minutes (14:03 to 14:05). Contributing factor: the pool limit went from 100 to 20 in the release config. No other cause was stated, so I added none. What went well: the on-call answered 2 minutes after the alert and the rollback took until 14:38. Action items: none stated yet. Tell me the follow-ups and I will list them with a role. Incident Postmortem Writer places a whole alert log and chat export in time, counts the durations by code, checks every quote word for word and keeps the action items on a board.

What it does for you

  • Places alert lines and chat in UTC and works out every duration
  • Writes a blameless postmortem, each point quoted word for word
  • Shows people as roles unless you keep their names
  • Says n/a when the material cannot support a duration
  • Keeps follow-up actions on a board you move to Done
  • Ignores any line that gives orders to an AI

The applications it runs

Postmortem Facilitator comes with these finished applications. Each one has its own page.

Published by

livecontext

livecontextOfficial LiveContext partner

@livecontext

Report this listing