Skip to main content

incident_pages

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

Overview

Nameincident_pages
TypeResource
Iddatadog.service_management.incident_pages

Fields

The following fields are returned by SELECT queries:

SELECT not supported for this resource, use SHOW METHODS to view available operations for the resource.

Methods

The following methods are available for this resource:

NameAccessible byRequired ParamsOptional ParamsDescription
create_on_call_page_from_incidentinsertincident_id, dataCreate an on-call page directly from an incident.
link_page_to_incidentexecincident_id, dataLink an existing on-call page to an incident.

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.

NameDatatypeDescription
incident_idstringThe UUID of the incident.
sitestringThe Datadog site (region) for your organization, for example datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com, ap2.datadoghq.com, datadoghq.eu, ddog-gov.com. Resolved from the DD_SITE environment variable when set. Optional: defaults to datadoghq.com, or the value of the DD_SITE environment variable when set; a WHERE value overrides both.

INSERT examples

Create an on-call page directly from an incident.

INSERT INTO datadog.service_management.incident_pages (
data,
incident_id
)
SELECT
'{{ data }}' /* required */,
'{{ incident_id }}'
RETURNING
data
;

Lifecycle Methods

EXEC variables use wire (API) names.

Link an existing on-call page to an incident.

EXEC datadog.service_management.incident_pages.link_page_to_incident
@incident_id='{{ incident_id }}' --required,
@@json=
'{
"data": "{{ data }}"
}'
;