Postmortems

The incident is resolved, everyone's asleep again, and the timeline is still warm. Postmortems turn that timeline into a written record — generated from the incident's audit trail, editable where the machines get it wrong, and exportable for the wiki or the PDF archive.

Before you start
  • An incident with some history — per Incidents & services. The postmortem is assembled from the incident's audit trail, so a blank incident makes a thin report.
  • Admin or team access to the incident. Anyone who can read the incident can generate and read its postmortem.
  1. Generate from the incident

    Open incident detail, scroll to the Postmortem section, optionally choose a template, and select Generate. OpsPing builds the timeline from the incident record and linked activity.

    Generate works best after the incident is resolved — then the whole trail exists and the report can state real durations instead of "still ongoing."

  2. Edit what the machine can't know

    Edit Summary, Root cause, and any template sections, then select Save. Structured action items are available through the postmortem API but are not currently editable in this console section.

    Refresh timeline rebuilds generated timeline content. Save editorial changes first; saved summary, root-cause, and template-section edits survive refresh, while unsaved local edits do not.

    Tip

    Write the postmortem within a day or two of resolving, while the details are fresh. A postmortem written from a fading memory is how the same incident happens twice.

  3. Export to Markdown or PDF

    When the report is ready, export it. Markdown drops straight into a repo or wiki; PDF is for the archive, auditors, or anyone who asks for "the report." Both exports reflect the current state of the postmortem, edits included.

    Use the export buttons on the postmortem view, or fetch the file via the API:

    curl "https://api.opsping.com/v2/postmortems/POSTMORTEM_ID/export?format=pdf" \
      -H "Authorization: OpsPingKey YOUR_API_KEY" \
      --output postmortem.pdf
    Note

    Swap format=pdf for format=md to get the Markdown export instead.

  4. Do it from the API

    Everything above is scriptable. Generate a postmortem for an incident:

    curl -X POST https://api.opsping.com/v2/postmortems/generate \
      -H "Authorization: OpsPingKey YOUR_API_KEY" \
      -H "Content-Type: application/json" \
      -d '{"incidentId": "INCIDENT_ID"}'

    The response includes the postmortem's id, which you use for the export call above. See the API reference for the full request and response shapes.