raw_responder_incidents

Creates, updates, deletes, gets or lists a raw_responder_incidents resource.

Overview

Name	raw_responder_incidents
Type	Resource
Id	pagerduty.analytics.raw_responder_incidents

Fields

The following fields are returned by SELECT queries:

list

Name	Datatype	Description
incident_id	string	Incident ID
incident_priority_id	string	ID of the incident's priority level.
responder_id	string	ID of the responder.
service_id	string	ID of the service that the incident triggered on.
service_team_id	string	ID of the team that owns the related service.
incident_priority_name	string	The user-provided short name of the priority.
responder_name	string	Name of the responder.
service_name	string	Name of the service that the incident triggered on.
service_team_name	string	Name of the team that owns the related service.
incident_created_at	string	Timestamp of when the incident was created.
incident_description	string	The incident description.
incident_number	integer	The PagerDuty incident number.
incident_priority_order	integer	The numerical value used to sort priorities. Higher values are higher priority.
incident_urgency	string	Notification level
mean_time_to_acknowledge_seconds	integer	Mean time from this user being assigned to an incident until this user acknowledges the incident.
total_acknowledgements	integer	Total acknowledgements from the responder on the incident.
total_business_hour_interruptions	integer	Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone.
total_engaged_seconds	integer	Total engaged time across all responders for incidents. Engaged time is measured from the time a user engages with an incident (by acknowledging or accepting a responder request) until the incident is resolved. This may include periods in which the incidents were snoozed.
total_interruptions	integer	Total number of unique interruptions for the responder during the incident.
total_manual_escalations_from	integer	Total times the responder was manually escalated away from the incident.
total_manual_escalations_to	integer	Total times the responder was manually escalated to the incident.
total_off_hour_interruptions	string	Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone.
total_reassignments_from	integer	Total times the responder was reassigned away from the incident.
total_reassignments_to	integer	Total times the responder was reassigned to the incident.
total_sleep_hour_interruptions	integer	Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.
total_timeout_escalations_from	integer	Total times the responder was escalated away from the incident due to timeout.
total_timeout_escalations_to	integer	Total times the responder was escalated to the incident due to timeout.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
list	select	responder_id		Provides enriched incident data and metrics for a specific responder.<br /><br />Example metrics include Mean Seconds to Resolve, Mean Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https:​//support.pagerduty.com/docs/insights#incidents-list).<br /><br /><!-- theme: info --><br />> Note: Data availability reflects [pipeline processing cycles](https:​//support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule) and is generally within 24 hours under normal conditions.<br /><br />Scoped OAuth requires: analytics.write<br />

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
responder_id	string	The ID of the responder.

SELECT examples

list

Provides enriched incident data and metrics for a specific responder.<br /><br />Example metrics include Mean Seconds to Resolve, Mean Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https:​//support.pagerduty.com/docs/insights#incidents-list).<br /><br /><!-- theme: info --><br />> Note: Data availability reflects [pipeline processing cycles](https:​//support.pagerduty.com/main/docs/insights#:~:text=Data%20Update%20Schedule) and is generally within 24 hours under normal conditions.<br /><br />Scoped OAuth requires: analytics.write<br />

SELECT
incident_id,
incident_priority_id,
responder_id,
service_id,
service_team_id,
incident_priority_name,
responder_name,
service_name,
service_team_name,
incident_created_at,
incident_description,
incident_number,
incident_priority_order,
incident_urgency,
mean_time_to_acknowledge_seconds,
total_acknowledgements,
total_business_hour_interruptions,
total_engaged_seconds,
total_interruptions,
total_manual_escalations_from,
total_manual_escalations_to,
total_off_hour_interruptions,
total_reassignments_from,
total_reassignments_to,
total_sleep_hour_interruptions,
total_timeout_escalations_from,
total_timeout_escalations_to
FROM pagerduty.analytics.raw_responder_incidents
WHERE responder_id = '{{ responder_id }}' -- required
;