event_orchestrations
Overview
| Name | event_orchestrations |
| Type | Resource |
| Id | pagerduty.event_orchestrations.event_orchestrations |
Fields
| Name | Datatype | Description |
|---|---|---|
id | string | ID of the Orchestration. |
name | string | Name of the Orchestration. |
description | string | A description of this Orchestration's purpose. |
created_at | string | The date the Orchestration was created at. |
created_by | object | Reference to the user that has created the Orchestration. |
integrations | array | |
routes | integer | Number of different Service Orchestration being routed to |
self | string | The API show URL at which the object is accessible |
team | object | Reference to the team that owns the Orchestration. If none is specified, only admins have access. |
updated_at | string | The date the Orchestration was last updated. |
updated_by | object | Reference to the user that has updated the Orchestration last. |
version | string | Version of the Orchestration. |
Methods
| Name | Accessible by | Required Params | Description |
|---|---|---|---|
get_orchestration | SELECT | id | Get a Global Event Orchestration. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.read |
list_event_orchestrations | SELECT | List all Global Event Orchestrations on an Account. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.read | |
delete_orchestration | DELETE | id | Delete a Global Event Orchestration. Once deleted, you will no longer be able to ingest events into PagerDuty using this Orchestration's Routing Key. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.write |
_get_orchestration | EXEC | id | Get a Global Event Orchestration. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.read |
_list_event_orchestrations | EXEC | List all Global Event Orchestrations on an Account. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.read | |
post_orchestration | EXEC | data__orchestration | Create a Global Event Orchestration. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.write |
update_orchestration | EXEC | id, data__orchestration | Update a Global Event Orchestration. Global Event Orchestrations allow you define a set of Global Rules and Router Rules, so that when you ingest events using the Orchestration's Routing Key your events will have actions applied via the Global Rules & then routed to the correct Service by the Router Rules, based on the event's content. For more information see the API Concepts Document Scoped OAuth requires: event_orchestrations.write |