pagerduty_incidents
Details about PagerDuty incidents
-
id
Primary key - Unique identifier of the row
-
source_id
Foreign key - Identifier of the incident in PagerDuty
-
service_id
Foreign key - ID of the service to which the incident belongs
-
incident_number
number - The number of the incident (unique to the account)
-
connection_id
Foreign key - ID of the Data Cloud connection importing the incident.
-
priority
string - Summary of the priority, often the same as name
-
source_url
string - URL of the incident
-
status
string - The current status of the incident
-
title
string - Title of the incident
-
urgency
string - Urgency level of the incident
-
alerts_all
number - Count of all alerts
-
alerts_triggered
number - Count of triggered alerts
-
alerts_resolved
number - Count of alerts resolved
-
created
date - Timestamp when the incident was created
-
resolved
date - Timestamp when the incident was resolved
-
auto_resolved
boolean - Boolean indicating if the incident auto resolved
-
unique_notifications
number - Count of unique notifications
-
ack_count
number - Number of acknowledged entries in incident logs
-
unack_count
number - Number of unacknowledged entries in incident logs
-
auto_escalations
number - Number of non-user escalations
-
user_escalations
number - Number of user escalations
-
seconds_to_first_ack
number - Seconds to the first ack
-
business_hour_interruptions
number - Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone
-
seconds_to_resolve
number - Time from when an incident was triggered until it was resolved
-
user_defined_effort_seconds
number - The total response effort in seconds, as defined by the user
-
off_hour_interruptions
number - Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone
-
sleep_hour_interruptions
number - Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone