incident_responders
Creates, updates, deletes, gets or lists an incident_responders resource.
Overview
| Name | incident_responders |
| Type | Resource |
| Id | datadog.service_management.incident_responders |
Fields
The following fields are returned by SELECT queries:
- get_incident_responder
- list_incident_responders
| Name | Datatype | Description |
|---|---|---|
id | string (uuid) | The responder identifier. (example: 00000000-0000-0000-0000-000000000000) |
attributes | object | Attributes of an incident responder in a response. |
relationships | object | Relationships for an incident responder. |
type | string | Incident responder resource type. (incident_responders) (example: incident_responders) |
| Name | Datatype | Description |
|---|---|---|
id | string (uuid) | The responder identifier. (example: 00000000-0000-0000-0000-000000000000) |
attributes | object | Attributes of an incident responder in a response. |
relationships | object | Relationships for an incident responder. |
type | string | Incident responder resource type. (incident_responders) (example: incident_responders) |
Methods
The following methods are available for this resource:
| Name | Accessible by | Required Params | Optional Params | Description |
|---|---|---|---|---|
get_incident_responder | select | incident_id, responder_id | Get a single responder for an incident. | |
list_incident_responders | select | incident_id | List all responders for an incident. | |
create_incident_responder | insert | incident_id, data | Add a responder to an incident. | |
delete_incident_responder | delete | incident_id, responder_id | Remove a responder from 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.
| Name | Datatype | Description |
|---|---|---|
incident_id | string | The UUID of the incident. |
responder_id | string (uuid) | The UUID of the incident responder. |
site | string | The 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. |
SELECT examples
- get_incident_responder
- list_incident_responders
Get a single responder for an incident.
SELECT
id,
attributes,
relationships,
type
FROM datadog.service_management.incident_responders
WHERE incident_id = '{{ incident_id }}' -- required
AND responder_id = '{{ responder_id }}' -- required
;
List all responders for an incident.
SELECT
id,
attributes,
relationships,
type
FROM datadog.service_management.incident_responders
WHERE incident_id = '{{ incident_id }}' -- required
;
INSERT examples
- create_incident_responder
- Manifest
Add a responder to an incident.
INSERT INTO datadog.service_management.incident_responders (
data,
incident_id
)
SELECT
'{{ data }}' /* required */,
'{{ incident_id }}'
RETURNING
data,
included
;
# Description fields are for documentation purposes
- name: incident_responders
props:
- name: incident_id
value: "{{ incident_id }}"
description: Required parameter for the incident_responders resource.
- name: data
description: |
Incident responder data in a create request.
value:
relationships:
user:
data:
id: "{{ id }}"
type: "{{ type }}"
type: "{{ type }}"
DELETE examples
- delete_incident_responder
Remove a responder from an incident.
DELETE FROM datadog.service_management.incident_responders
WHERE incident_id = '{{ incident_id }}' --required
AND responder_id = '{{ responder_id }}' --required
;