StatusPulse StatusPulse
← All features

Incidents · Starter+

Incident CSV export

One "Export CSV" button on the incident detail page. Compliance audits, customer post-incident requests, internal RCA write-ups — all start with the same row dump.

Why you need it

The CSV is structured in sections so spreadsheet tools pivot cleanly: metadata header, components, full timeline, and the SLO impact rows from the incident detail page.

  • RFC 4180 escaping. Fields with commas, quotes, or newlines wrap correctly; Excel / Google Sheets / LibreOffice all open without manual fixup.
  • SLO impact included. Each affected component carries uptime%, downtime, SLA target, and error-budget burn — feeds compliance reviewers chasing SLA-breach correlation.
  • Predictable filename. incident-<shortId>-<date>.csv so files sort naturally in a compliance folder.
  • Internal-incident-aware. The export includes the "Internal" flag in metadata so a compliance reviewer knows the visibility scope.

Where it pays off

The most boring but most-asked-for compliance feature:

  • SOC 2 / ISO 27001 evidence collection. Auditor asks for an incident sample — you export ten CSVs.
  • Customer post-incident requests. "Send us the timeline." One button, one file.
  • Internal retros. Pivot in Excel for the patterns the dashboard doesn't natively show.

Available on Starter+. Already on StatusPulse? See the full config in Help →

Related

Try Incident CSV export in StatusPulse

5 probes, 1 status page, forever. No credit card. US or EU host — you choose.

Start free See pricing