Source
Incident response, status pages & post-incident review — found from sitemap — PagerDuty
Checked for PagerDuty on 6 Nov 2026
- Page
- https://docs.pagerduty.com/incident-management/incidents/overview
- Checked
- 6 Nov 2026, 04:49 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:e9ee16ef13d44e4a0623ac0b03d9cb6c4805f1f17f297892489b255946f8afd0
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
Incident statuses Report an error
“Triggered: An active service (i.e., someone is on call and the service is not disabled or in maintenance mode) triggers an incident when it receives an event.”
-
Acknowledgement behavior Report an error
“The user who acknowledges an incident claims ownership of the issue and halts the escalation process. While an incident is acknowledged, notifications are not sent until the acknowledgement timeout is reached.”
-
Resolved reopen Report an error
“Once an incident is resolved, no additional notifications are sent. You can reopen it if further work is needed.”
-
Priority definition Report an error
“Priority is tied to incidents, and it specifies the order in which incidents must be addressed (e.g., P1, Sev-1).”
-
Severity definition Report an error
“Severity is tied to alerts and describes the impact on a specific service or piece of infrastructure (e.g., critical, warning, error).”
-
Urgency definition Report an error
“Urgency is tied to incidents and determines how are notified when an incident is assigned to you (high or low).”
-
Notification channels Report an error
“Notifications via Push, Phone, Slack, Email, or SMS”
-
Incidents require oncall Report an error
“Incidents are only created when an escalation policy has an on-call user.”
-
Incident timeline Report an error
“Each incident has a Timeline tab in the incident details page, showing timestamps of each incident status along with all other actions taken and notifications sent from the incident.”
-
Trigger methods Report an error
“Trigger an Incident via Integration Declare an Incident via Web App Declare an Incident via Mobile App Trigger an Incident via API Declare an Incident via Email Integration Declare an Incident via Slack”
-
Trigger event limit Report an error
“An incident stops accepting new trigger events after receiving 100 events with the same deduplication key.”
-
Auto resolve high volume Report an error
“For services with over 100K open incidents, the auto-resolve feature will automatically be enabled. With this feature enabled, all new incidents for that particular service are auto-resolved after 24 hours, and no further notifications will be sent for those incidents.”
-
Acknowledgement limit Report an error
“Each incident is limited to 100 acknowledgements. However, the limit for added responders is 1000.”
-
Suppress alert Report an error
“Use Suppress alert to collect data without triggering an incident or notifying responders.”
-
Alert acknowledgement Report an error
“Alerts cannot be acknowledged; they can only be triggered or resolved.”
-
Alert incident resolution link Report an error
“If all alerts in an incident are resolved, the incident gets resolved. Similarly, when an incident is resolved, all associated alerts are also resolved.”
-
Unacknowledge Report an error
“If you accidentally acknowledge an incident, you can undo it by clicking the More... button in the incident details page and selecting Unacknowledge Incident.”
-
Redact incident Report an error
“If an incident contains sensitive information, the Account Owner can permanently delete the incident's details by selecting More... and clicking the Redact Incident button.”
-
Redaction analytics impact Report an error
“Redacting deletes the incident description and incident key, but does not affect Analytics metrics associated with the incident.”
-
Incident numbers skip Report an error
“PagerDuty never deletes incidents, so a skipped number means it was skipped at creation time.”
Scores citing this record
- The Engineering Manager Alert delivery, routing & noise reduction
- The Engineering Manager Incident response, status pages & post-incident review
- The ICT Risk Officer Alert delivery, routing & noise reduction
- The ICT Risk Officer Incident response, status pages & post-incident review
- The IT Operations Manager Alert delivery, routing & noise reduction
- The IT Operations Manager Incident response, status pages & post-incident review
- The MSP NOC Lead Alert delivery, routing & noise reduction
- The MSP NOC Lead Incident response, status pages & post-incident review
- The Skeptic Alert delivery, routing & noise reduction
- The Skeptic Incident response, status pages & post-incident review
- The SRE Lead Alert delivery, routing & noise reduction
- The SRE Lead Incident response, status pages & post-incident review
- The SRE Lead Integrations, API & administration