Note that to create an incident you need to trigger it through the events API.
PagerDuty receives updates (called events) from monitoring systems through services (like Nagios, email or generic API calls). Upon receiving an event, active services will create a new incident and begin escalating it as defined by the service's escalation policy. Events can be de-duplicated into existing incidents based on service de-duplication rules to prevent you from being overwhelmed by event storms.
An incident can be open, acknowledged or resolved. Whenever an incident is created, it is assigned to a user (according to the escalation process, as described by escalation rules and schedules). The assigned user has a chance to either acknowledge that he is working on it, or to resolve it.
Resolving an incident closes it, whereas acknowledging it halts the escalation process. If the incident is not resolved by the service's incident ack timeout it continues up the escalation chain.
When an incident is triggered or when it is escalated it creates alerts (also known as notifications). Alerts are messages containing the details of the incident, and can be sent through SMS, email and phone calls.
Incidents and Incident Counts from the last 30 days are returned by default. To change this default date range, see the documentation for the
|GET incidents||List existing incidents.|
|GET incidents/:id||Show detailed information about an incident. Accepts either an incident id, or an incident number.|
|GET incidents/count||Count the number of incidents matching certain criteria.|
|PUT incidents||Acknowledge, resolve, escalate or reassign one or more incidents.|
|PUT incidents/:id/resolve||Resolve an incident.|
|PUT incidents/:id/acknowledge||Acknowledge an incident.|
|PUT incidents/:id/reassign||Reassign an incident.|
|PUT incidents/:id/snooze||Snooze an incident.|