Skip to content

Post-Mortems ​

Alga provides a structured, blameless post-mortem workflow for incidents, with review/approval processes and trackable action items. Each post-mortem is linked 1:1 to an incident (incident_id is unique).

Post-Mortem Lifecycle ​

draft → in_review → approved → published
StatusDescription
draftInitial creation, being written
in_reviewSubmitted for review
approvedReviewed and approved (records approved_by_id)
publishedPublicly visible (records published_at)

Allowed transitions: draft → in_review; in_review → draft or approved; approved → in_review or published. Submitting for review notifies the incident commander that a review is requested.

Content Fields ​

A post-mortem includes the following fields:

FieldDescription
titlePost-mortem title
summaryBrief description of what happened
timelineKey events during the incident (structured JSON)
root_causeTechnical explanation
contributing_factorsAdditional factors that contributed (list)
impactDuration, affected services, user impact
what_went_wellThings that worked during the response
what_went_wrongThings that did not work or could be improved
lessons_learnedWhat was learned and what could be improved
blameless_confirmedAcknowledgement that the review is blameless
blameless_notesNotes supporting the blameless confirmation

AI Draft Builder ​

When an incident is resolved, Alga can auto-create a post-mortem draft pre-populated from incident context — the incident document sections, coordination messages, timeline entries, status updates, and linked alerts. The same enrichment logic backs both the operator resolve flow and the agent resolve tool.

Action Items ​

Action items are tracked per post-mortem and can be assigned, prioritized, and driven to completion.

FieldDescription
descriptionWhat needs to be done (required)
typeKind of follow-up (defaults to investigate)
assignee_id / assignee_nameUser responsible
statusopen → in_progress → done (defaults to open)
priorityPriority level (defaults to medium)
due_dateTarget completion date

View all open action items globally at GET /api/v1/action-items.

Workflow ​

  1. Create the post-mortem (auto-drafted on resolve, or created manually)
  2. Edit content as needed (while in draft)
  3. Submit for Review — moves to in_review and notifies the commander
  4. Approve — moves to approved and records the approver
  5. Publish — moves to published
  6. Track Action Items — ensure follow-up tasks are completed

API Endpoints ​

Post-Mortem Management ​

MethodPathAuthPermissionDescription
GET/api/v1/post-mortemsSessionpostmortems:readList all post-mortems
GET/api/v1/incidents/{id}/post-mortemSessionpostmortems:readGet post-mortem
POST/api/v1/incidents/{id}/post-mortemSessionpostmortems:writeCreate post-mortem
PATCH/api/v1/incidents/{id}/post-mortemSessionpostmortems:writeUpdate post-mortem
DELETE/api/v1/incidents/{id}/post-mortemSessionpostmortems:deleteDelete post-mortem

Workflow Actions ​

MethodPathAuthPermissionDescription
POST/api/v1/incidents/{id}/post-mortem/submit-reviewSessionpostmortems:writeSubmit for review (in_review)
POST/api/v1/incidents/{id}/post-mortem/approveSessionpostmortems:writeApprove post-mortem
POST/api/v1/incidents/{id}/post-mortem/publishSessionpostmortems:writePublish post-mortem

Action Items ​

MethodPathAuthPermissionDescription
GET/api/v1/incidents/{id}/post-mortem/action-itemsSessionpostmortems:readList action items
POST/api/v1/incidents/{id}/post-mortem/action-itemsSessionpostmortems:writeCreate action item
PATCH/api/v1/incidents/{id}/post-mortem/action-items/{itemId}Sessionpostmortems:writeUpdate action item
DELETE/api/v1/incidents/{id}/post-mortem/action-items/{itemId}Sessionpostmortems:deleteDelete action item

Global Action Items ​

MethodPathAuthPermissionDescription
GET/api/v1/action-itemsSessionpostmortems:readAll open action items

See Also ​

Released under the MIT License.