incident_metrics_all_escalation_policies

Creates, updates, deletes, gets or lists an incident_metrics_all_escalation_policies resource.

Overview

Name	incident_metrics_all_escalation_policies
Type	Resource
Id	pagerduty.analytics.incident_metrics_all_escalation_policies

Fields

The following fields are returned by SELECT queries:

list

Only returns data for escalation policies that match the filters and have data.

Name	Datatype	Description
escalation_policy_id	string	ID of the escalation policy the incident was last assigned to. Not included when aggregating by all.
team_id	string	ID of the team the incident was assigned to. Not included when aggregating by all.
escalation_policy_name	string	Name of the escalation policy the incident was last assigned to. Not included when aggregating by all.
team_name	string	Name of the team the incident was assigned to. Not included when aggregating by all.
distinct_responder_count	integer	Distinct count of responders who engaged in incidents on the escalation policy
mean_assignment_count	integer	Mean count of instances where responders were assigned an incident (including through reassignment or escalation) or accepted a responder request.
mean_engaged_seconds	integer	Mean engaged time across all responders. 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_engaged_user_count	integer	Mean number of users who engaged with an incident. Engaged is defined as acknowledging an incident or accepting a responder request in it.
mean_seconds_to_engage	integer	A measure of people response time. This metric measures the time from the first user engagement (acknowledge or responder accept) to the last. This metric is only used for incidents with multiple responders; for incidents with one or no engaged users, this value is null.
mean_seconds_to_first_ack	integer	Mean time between the start of an incident, and the first responder to acknowledge.
mean_seconds_to_mobilize	integer	Mean time between the start of an incident, and the last additional responder to acknowledge. For incidents with one or no engaged users, this value is null.
mean_seconds_to_resolve	integer	Mean time from when an incident was triggered until it was resolved.
mean_user_defined_engaged_seconds	integer	Mean engaged time across all responders. 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. This metric uses the incident response effort values that [users have defined](https:​//support.pagerduty.com/docs/edit-incidents#edit-incident-duration), if they exist.
range_start	string	Start of the date range that the metrics were calculated for. Only included when an aggregate unit is specified in the request.
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. 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_escalation_count	integer	Total count of instances where an incident is escalated between responders assigned to an escalation policy.
total_incident_count	integer	The total number of incidents that were created.
total_incidents_acknowledged	integer	The total count of assigned incidents acknowledged. Only explicit incident acknowledgment counts; reassign, resolve, and escalation actions do not imply acknowledgement.
total_incidents_auto_resolved		The total count of incidents that were resolved automatically. This count includes incidents resolved via an integration and those that were [auto-resolved in PagerDuty](https:​//support.pagerduty.com/docs/configurable-service-settings#auto-resolution).
total_incidents_manual_escalated	integer	The total count of incidents that were manually escalated.
total_incidents_reassigned	integer	The total count of incidents that were reassigned.
total_incidents_timeout_escalated	integer	The total count of incidents that were escalated 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_sleep_hour_interruptions	integer	Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.
total_snoozed_seconds	integer	Total number of seconds incidents were snoozed.
total_user_defined_engaged_seconds	integer	Total engaged time across all responders. 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. This metric uses the edited incident response effort values that [users have defined](https:​//support.pagerduty.com/docs/edit-incidents#edit-incident-duration), if they exist.
up_time_pct	number	The percentage of time in the defined date range that the service was not interrupted by a [major incident](https:​//support.pagerduty.com/docs/operational-reviews#major-incidents). Not included when aggregating by all.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
list	select			Provides aggregated metrics across all escalation policies.<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#escalation-policy-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 aggregated metrics across all escalation policies.<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#escalation-policy-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
escalation_policy_id,
team_id,
escalation_policy_name,
team_name,
distinct_responder_count,
mean_assignment_count,
mean_engaged_seconds,
mean_engaged_user_count,
mean_seconds_to_engage,
mean_seconds_to_first_ack,
mean_seconds_to_mobilize,
mean_seconds_to_resolve,
mean_user_defined_engaged_seconds,
range_start,
total_business_hour_interruptions,
total_engaged_seconds,
total_escalation_count,
total_incident_count,
total_incidents_acknowledged,
total_incidents_auto_resolved,
total_incidents_manual_escalated,
total_incidents_reassigned,
total_incidents_timeout_escalated,
total_interruptions,
total_notifications,
total_off_hour_interruptions,
total_sleep_hour_interruptions,
total_snoozed_seconds,
total_user_defined_engaged_seconds,
up_time_pct
FROM pagerduty.analytics.incident_metrics_all_escalation_policies
;