responder_metrics_by_team

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

Overview

Name	responder_metrics_by_team
Type	Resource
Id	pagerduty.analytics.responder_metrics_by_team

Fields

The following fields are returned by SELECT queries:

list

Only returns data for responders and teams that match the filters and have data.

Name	Datatype	Description
responder_id	integer	ID of the responder (user). Not included when aggregating by all responders.
team_id	string	ID of the team associated with the responder. Not included when aggregating by all responders.
responder_name	string	Name of the responder (user). Not included when aggregating by all responders.
team_name	string	Name of the team associated with the responder. Not included when aggregating by all responders.
mean_engaged_seconds	integer	Mean engaged time across all responders for incidents that match the given filters. 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.
mean_time_to_acknowledge_seconds	integer	The average time between when an incident is first assigned to a user and when the incident is first acknowledged by that user. Reassign, resolve, and escalation actions do not imply acknowledgement.
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_incident_count	integer	The total number of incidents that were created.
total_incidents_acknowledged	integer	The total count of assigned incidents acknowledged by the user. Only explicit incident acknowledgment counts; reassign, resolve, and escalation actions do not imply acknowledgement.
total_incidents_manual_escalated_from	integer	The total count of the user’s assigned incidents that were manually escalated away from a user without acknowledgement.
total_incidents_manual_escalated_to	integer	The total count of incidents the user was manually escalated to.
total_incidents_reassigned_from	integer	The total count of a user's assigned incidents that were reassigned away from the user to another user or escalation policy.
total_incidents_reassigned_to	integer	The total count of incidents the user was reassigned to.
total_incidents_timeout_escalated_from	integer	The total count of the user’s assigned incidents that were escalated due to timeouts.
total_incidents_timeout_escalated_to	integer	The total count of incidents the user was escalated to due to timeouts.
total_interruptions	integer	Total number of unique interruptions.
total_notifications	integer	The total count of incident notifications sent via email, SMS, phone call and push.
total_off_hour_interruptions	integer	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_seconds_on_call	integer	Total seconds the responder was on call.
total_seconds_on_call_level_1	integer	Total seconds the responder was on call at level 1 of their escalation policy.
total_seconds_on_call_level_2_plus	integer	Total seconds the responder was on call at level 2 or higher of their escalation policy.
total_sleep_hour_interruptions	integer	Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
list	select			Provides incident metrics aggregated by responder.<br /><br />Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https:​//support.pagerduty.com/docs/insights#responders-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

SELECT examples

list

Provides incident metrics aggregated by responder.<br /><br />Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our [Knowledge Base](https:​//support.pagerduty.com/docs/insights#responders-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
responder_id,
team_id,
responder_name,
team_name,
mean_engaged_seconds,
mean_time_to_acknowledge_seconds,
total_business_hour_interruptions,
total_engaged_seconds,
total_incident_count,
total_incidents_acknowledged,
total_incidents_manual_escalated_from,
total_incidents_manual_escalated_to,
total_incidents_reassigned_from,
total_incidents_reassigned_to,
total_incidents_timeout_escalated_from,
total_incidents_timeout_escalated_to,
total_interruptions,
total_notifications,
total_off_hour_interruptions,
total_seconds_on_call,
total_seconds_on_call_level_1,
total_seconds_on_call_level_2_plus,
total_sleep_hour_interruptions
FROM pagerduty.analytics.responder_metrics_by_team
;