PApagerduty
Analytics

Get raw data - single incident

Provides enriched incident data and metrics for a single incident.

Example metrics include Seconds to Resolve, Seconds to Engage, Snoozed Seconds, and Sleep Hour Interruptions. Metric definitions can be found in our Knowledge Base.

<!-- theme: info -->

Note: Data availability reflects pipeline processing cycles and is generally within 24 hours under normal conditions.

Scoped OAuth requires: analytics.read

get/analytics/raw/incidents/{id}

Request

Headers

Acceptstring required

The Accept header is used as a versioning header.

Content-Type'application/json' required

Response

acknowledged_user_idsstring[]

The IDs of the users who acknowledged the incident.

acknowledged_user_namesstring[]

The names of the users who acknowledged the incident.

acknowledgement_countinteger

Total count of acknowledgements in the incident.

active_user_countinteger

Total number of responders who either acknowledged the incident or accepted a responder request.

assigned_user_idsstring[]

The IDs of the users who were assigned the incident.

assigned_user_namesstring[]

The names of the users who were assigned the incident.

assignment_countinteger

Total count of instances where responders were assigned an incident (including through reassignment or escalation).

auto_resolvedboolean

Whether or not the incident resolved automatically, either via an integration or auto-resolved in PagerDuty.

business_hour_interruptionsinteger

Total number of unique interruptions during business hours; 8am-6pm Mon-Fri, based on the user’s time zone.

created_atstring

Timestamp of when the incident was created.

updated_atstring

Timestamp of when the incident was last updated by the analytics process. Does not match the updated_at for an incident returned by the standard REST api incidents endpoint.

descriptionstring

The incident description

engaged_secondsinteger

Total engaged time across all responders for this incident. 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.

engaged_user_countinteger

Total number of users who engaged (acknowledged, accepted responder request) in the incident.

escalation_countinteger

Total count of instances where an incident is escalated between responders assigned to an escalation policy.

escalation_policy_idstring

ID of the escalation policy the incident was assigned to.

escalation_policy_namestring

Name of the escalation policy the incident was assigned to.

idstring

Incident ID

incident_numberinteger

The PagerDuty incident number.

incident_type_idstring

ID of the Incident Type.

incident_type_namestring

The name of the Incident Type.

joined_user_idsstring[]

The IDs of the users who either acknowledged the incident or accepted a responder request.

joined_user_namesstring[]

The names of the users who either acknowledged the incident or accepted a responder request.

majorboolean

An incident is classified as a major incident if it has one of the two highest priorities, or if multiple responders are added and acknowledge the incident.

manual_escalation_countinteger

Total count of manual escalations in the incident.

off_hour_interruptionsinteger

Total number of unique interruptions during off hours; 6pm-10pm Mon-Fri and all day Sat-Sun, based on the user’s time zone.

priority_idstring nullable

ID of the incident's priority level.

priority_namestring nullable

The user-provided short name of the priority.

priority_orderinteger nullable

The numerical value used to sort priorities. Higher values are higher priority.

reassignment_countinteger

Total count of reassignments in the incident.

resolved_atstring

Timestamp of when the incident was resolved.

resolved_by_user_idstring

ID of the user who resolved the incident.

resolved_by_user_namestring

Name of the user who resolved the incident.

seconds_to_engageinteger

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.

seconds_to_first_ackinteger

Time between the start of an incident, and the first responder to acknowledge.

seconds_to_mobilizeinteger

Time between the start of an incident, and the last additional responder to acknowledge. If an incident has one or no responders, the value will be null.

seconds_to_resolveinteger

Time from when an incident was triggered until it was resolved.

service_idstring

ID of the service that the incident triggered on.

service_namestring

Name of the service that the incident triggered on.

sleep_hour_interruptionsinteger

Total number of unique interruptions during sleep hours; 10pm-8am every day, based on the user’s time zone.

snoozed_secondsinteger

Total seconds the incident has been snoozed for.

statusstring

The incident status. Can be one of triggered, acknowledged, or resolved.

team_idstring nullable

ID of the team the incident was assigned to.

team_namestring nullable

Name of the team the incident was assigned to.

timeout_escalation_countinteger

Total count of timeout escalations in the incident.

total_interruptionsinteger

Total number of unique interruptions in the incident.

total_notificationsinteger

Total number of notifications sent for the incident.

urgencystring

Notification level

user_defined_effort_secondsinteger nullable

The total response effort in seconds, as defined by the user.

Changes

No recorded changes to this operation across all 1 revision of this API.