incident_change_events

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

Overview

Name	incident_change_events
Type	Resource
Id	pagerduty.change_events.incident_change_events

Fields

The following fields are returned by SELECT queries:

list

The array of Change Events returned by the query.

Name	Datatype	Description
id	string
correlation_reason	object
custom_details	string	Additional details about the change event. (opaque JSON object) (title: Custom Details)
html_url	string (url)	a URL at which the entity is uniquely displayed in the Web app
images	array
integration	object	(opaque JSON object)
links	array	List of links to include.
routing_key	string	This is the 32 character Integration Key for an Integration on a Service. The same Integration Key can be used for both alert and change events. (title: Routing Key)
self	string (url)	the API show URL at which the object is accessible
services	array	An array containing Service objects that this change event is associated with.
source	string	The unique name of the location where the Change Event occurred.
summary	string	A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name, though it is not intended to be an identifier.
timestamp	string (date-time)	The time at which the emitting tool detected or generated the event.
type	string	A string that determines the schema of the object. This must be the standard name for the entity, suffixed by _reference if the object is a reference.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
list	select	id	limit	List related Change Events for an Incident, as well as the reason these changes are correlated with the incident.<br /><br />Change events represent service changes such as deploys, build completion, and configuration changes, providing information that is critical during incident triage or hypercare. For more information on change events, see [Change Events](https:​//support.pagerduty.com/docs/change-events).<br /><br />The Change Correlation feature provides incident responders with recent change events that are most relevant to that incident. Change Correlation informs the responder why a particular change event was surfaced and correlated to an incident based on three key factors which include time, related service, or intelligence (machine learning).<br /><br />Scoped OAuth requires: incidents.read<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
id	string	The ID of the resource.
limit	integer	The number of results per page.

SELECT examples

list

List related Change Events for an Incident, as well as the reason these changes are correlated with the incident.<br /><br />Change events represent service changes such as deploys, build completion, and configuration changes, providing information that is critical during incident triage or hypercare. For more information on change events, see [Change Events](https:​//support.pagerduty.com/docs/change-events).<br /><br />The Change Correlation feature provides incident responders with recent change events that are most relevant to that incident. Change Correlation informs the responder why a particular change event was surfaced and correlated to an incident based on three key factors which include time, related service, or intelligence (machine learning).<br /><br />Scoped OAuth requires: incidents.read<br />

SELECT
id,
correlation_reason,
custom_details,
html_url,
images,
integration,
links,
routing_key,
self,
services,
source,
summary,
timestamp,
type
FROM pagerduty.change_events.incident_change_events
WHERE id = '{{ id }}' -- required
AND limit = '{{ limit }}'
;