Event Orchestrations allow you define a set of Event Rules, so that when you ingest events using the Orchestration's Routing Key your events will be routed to the correct Global and/or Service Orchestration, based on the event's content.
resource "pagerduty_team" "engineering" {
name = "Engineering"
}
resource "pagerduty_event_orchestration" "my_monitor" {
name = "My Monitoring Orchestration"
description = "Send events to a pair of services"
team = pagerduty_team.engineering.id
}
The following arguments are supported:
name
- (Required) Name of the Event Orchestration.description
- (Optional) A human-friendly description of the Event Orchestration.team
- (Optional) ID of the team that owns the Event Orchestration. If none is specified, only admins have access.The following attributes are exported:
id
- The ID of the Event Orchestration.integration
- An integration for the Event Orchestration.
id
- ID of the integrationparameters
routing_key
- Routing key that routes to this Orchestration.type
- Type of the routing key. global
is the default type.EventOrchestrations can be imported using the id
, e.g.
$ terraform import pagerduty_event_orchestration.main 19acac92-027a-4ea0-b06c-bbf516519601