{'type': 'object', 'properties': {'id': {'type': 'string', 'example': 'p31zjtct2jer', 'description': 'Incident Identifier'}, 'components': {'type': 'array', 'items': {'$ref': '#/components/schemas/Component'}, 'description': 'Incident components'}, 'created_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when the incident was created at.'}, 'impact': {'type': 'string', 'example': 'critical', 'enum': ['none', 'maintenance', 'minor', 'major', 'critical'], 'description': 'The impact of the incident.'}, 'impact_override': {'type': 'string', 'example': 'minor', 'enum': ['none', 'maintenance', 'minor', 'major', 'critical'], 'description': 'value to override calculated impact value'}, 'incident_updates': {'type': 'array', 'items': {'$ref': '#/components/schemas/IncidentUpdate'}, 'description': 'The incident updates for incident.'}, 'metadata': {'type': 'Object', 'example': {'jira': {'issue_id': 'value'}}, 'description': 'Metadata attached to the incident. Top level values must be objects.'}, 'monitoring_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when incident entered monitoring state.'}, 'name': {'type': 'string', 'example': 'Data Layer Migration', 'description': 'Incident Name. There is a maximum limit of 255 characters.'}, 'page_id': {'type': 'string', 'description': 'Incident Page Identifier'}, 'postmortem_body': {'type': 'string', 'example': '##### Issue\nAt approximately 17:02 UTC on 2013-04-21, our master database server unexpectedly went unresponsive to all network.\nA reboot of the machine at 17:05 UTC resulted in a failed mount of a corrupted EBS volume, and we made the decision\nat that time to fail over the slave database.\n\n##### Resolution\nAt 17:12 UTC, the slave database had been successfully promoted to master and the application recovered enough to\naccept web traffic again. A new slave database node was created and placed into the rotation to guard against future\nmaster failures. The promoted slave database performed slowly for the next couple of hours as the query cache began\nto warm up, and eventually settled into a reasonable performance profile around 20:00 UTC.\n\n##### Future Mitigation Plans\nOver the past few months, we have been working on an overhaul to our data storage layer with a migration from a Postgres\nsetup to a distributed, fault-tolerant, multi-region data layer using Riak. This initiative has been prioritized, and\nthe migration will be performed in the coming weeks. We will notify our clients of the scheduled downtime via an\nincident on this status site, and via a blog post.\n', 'description': 'Body of the Postmortem.'}, 'postmortem_body_last_updated_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when the incident postmortem body was last updated at.'}, 'postmortem_ignored': {'type': 'boolean', 'description': 'Controls whether the incident will have postmortem.'}, 'postmortem_notified_subscribers': {'type': 'boolean', 'description': 'Indicates whether subscribers are already notificed about postmortem.'}, 'postmortem_notified_twitter': {'type': 'boolean', 'description': 'Controls whether to decide if notify postmortem on twitter.'}, 'postmortem_published_at': {'type': 'boolean', 'description': 'The timestamp when the postmortem was published.'}, 'resolved_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when incident was resolved.'}, 'scheduled_auto_completed': {'type': 'boolean', 'description': 'Controls whether the incident is scheduled to automatically change to complete.'}, 'scheduled_auto_in_progress': {'type': 'boolean', 'description': 'Controls whether the incident is scheduled to automatically change to in progress.'}, 'scheduled_for': {'type': 'string', 'format': 'date-time', 'example': '2013-05-07T03:00:00.007Z', 'description': 'The timestamp the incident is scheduled for.'}, 'auto_transition_deliver_notifications_at_end': {'type': 'boolean', 'description': 'Controls whether send notification when scheduled maintenances auto transition to completed.'}, 'auto_transition_deliver_notifications_at_start': {'type': 'boolean', 'description': 'Controls whether send notification when scheduled maintenances auto transition to started.'}, 'auto_transition_to_maintenance_state': {'type': 'boolean', 'description': 'Controls whether change components status to under_maintenance once scheduled maintenance is in progress.'}, 'auto_transition_to_operational_state': {'type': 'boolean', 'description': 'Controls whether change components status to operational once scheduled maintenance completes.'}, 'scheduled_remind_prior': {'type': 'boolean', 'description': 'Controls whether to remind subscribers prior to scheduled incidents.'}, 'scheduled_reminded_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when the scheduled incident reminder was sent at.'}, 'scheduled_until': {'type': 'string', 'format': 'date-time', 'example': '2013-05-07T06:00:00.007Z', 'description': 'The timestamp the incident is scheduled until.'}, 'shortlink': {'type': 'string', 'example': 'http://stspg.io/803310a12', 'description': 'Incident Shortlink.'}, 'status': {'type': 'string', 'example': 'scheduled', 'enum': ['investigating', 'identified', 'monitoring', 'resolved', 'scheduled', 'in_progress', 'verifying', 'completed'], 'description': 'The incident status. For realtime incidents, valid values are investigating, identified, monitoring, and resolved. For scheduled incidents, valid values are scheduled, in_progress, verifying, and completed.'}, 'updated_at': {'type': 'string', 'format': 'date-time', 'description': 'The timestamp when the incident was updated at.'}, 'reminder_intervals': {'type': 'string', 'example': '[3, 6, 12, 24]', 'description': 'Custom reminder intervals for unresolved/open incidents. Not applicable for Scheduled maintenance
There are 4 possible states for reminder_intervals:
DEFAULT: NULL, representing a default behavior with intervals [3, 6, 12, 24].
AFTER: A serialized array of strictly increasing intervals, each integer ranges from [1-24] (inclusive). Ex "[1, 5, 7, 10]"
EVERY: An integer in the range [1-24] as a string, representing equal intervals. Ex "4" for [4, 8, 12, 16, 20, 24]
OFF: A serialized empty array, for example, "[]", meaning no reminder notifications will be sent.'}}, 'description': 'Get an incident'} is not valid under any of the given schemas