OpsKnightDraft. Review. Publish.
Separate investigation from the published review. Distinguish observed facts from hypotheses and write for system improvement rather than individual blame.
Read the operational guidePOSTMORTEMS
Make the next incident easier.
Turn resolved incidents into reviews with a timeline, contributing factors and owned follow-up work.
WHAT IT SOLVES
Start from the incident evidence.
Connect impact, detection, response and resolution to the source timeline. Preserve evidence links so the review remains traceable to the incident record.
Understand the capability01Incident timeline
02Interactive 5 Whys
03Action items with owners and due dates
OPSKNIGHT / PRODUCT VIEW Northstar Systems · v2.0.0
HOW IT WORKS
A concrete operational path, not a feature list.
LEARNING LOOPMove from evidence to an owned, verifiable operational change.
01Timeline
02Draft review
035 Whys
04Action items
05Verify
EXPLORE A WORKFLOW
- 01Resolved incident
- 02Timeline
- 03Impact & detection
- 04Contributing factors
Begin with the incident record and distinguish observed facts from hypotheses before writing the review.
OPERATIONAL DEPTH
Postmortems, beyond the happy path.
The details below are the parts teams need when evaluating how the capability behaves during real response, failure, and handoff.
Learning needs an owner.
Track follow-up action items with an owner and status. Close remediation work when it is verifiably complete, rather than when the incident review is written.
Read the operational guideCarry the change into the next response.
Review detection gaps, response friction and contributing conditions together. Use the documented workflow to keep review and publication deliberate.
Read the operational guideKNOW BEFORE PRODUCTION
Validate the boundary, not just the happy path.
Use a test service and representative provider configuration before treating postmortems as production incident infrastructure.
- 01Preserve incident evidence links and distinguish observed facts from hypotheses.
- 02Give every follow-up action a clear owner and due date.
- 03Verify remediation is complete rather than treating publication as the finish line.
DOCUMENTATIONSetup, authorization, limits, and troubleshooting.
Explore postmortems documentationYour incidents should belong to you.
Run OpsKnight on infrastructure you control.
v2.0.0 · AGPL-3.0-only · Self-hosted · 28 inbound integrations