Entity · major_incidents
Major Incident Schema
Felder
Major Incident Schema
Coordinates work across many related tickets caused by the same underlying outage / brand event
title
Short headline of the incident
1–500 Zeichen
description
max 10000 Zeichennullable
severity
Severity (SEV1 = full outage, SEV4 = minor)
Werte
SEV1SEV2SEV3SEV4status
Werte
INVESTIGATINGIDENTIFIEDMONITORINGRESOLVEDPOSTMORTEMCLOSEDDefault: "INVESTIGATING"
commanderId
Incident commander / Major Incident Manager
nullable
masterTicketId
Optional reference ticket representing the incident
nullable
childTicketIds
Tickets caused by this incident
Default: []read-only
affectedServiceIds
Services / assets impacted
Default: []
affectedPartyIds
Customer parties impacted
Default: []
detectedAt
nullable
resolvedAt
nullable
postmortemUrl
max 1000 Zeichennullable
Keine Felder passen zum Filter.
Standard-Endpoints
Diese Resource folgt dem generischen CRUD-Vertrag der Plattform. Lesen Sie die Konventionen für Pagination, Idempotenz, Optimistic Locking und Audit. Die wichtigsten Endpoints:
GET /api/v1/major_incidents— Liste, paginiert + filterbarGET /api/v1/major_incidents/<id>— Einzelne EntityPOST /api/v1/major_incidents— AnlegenPATCH /api/v1/major_incidents/<id>— Teil-UpdateDELETE /api/v1/major_incidents/<id>— Soft-DeleteGET /api/v1/major_incidents/<id>/timeline— Audit + Aktivitäten