Configure PagerDuty Event Orchestrations with routing rules to replace deprecated Rulesets

Steps

1. Create a global Event Orchestration: POST /event_orchestrations with a name and team reference; note the orchestration's integration_key for use as the ingest endpoint
2. Configure the router layer: PUT /event_orchestrations/{id}/router with a rules array; each rule has conditions (field path + operator + value) and an actions object specifying route_to with a service ID
3. Add a catch-all rule as the last entry in the rules array with an empty conditions array to route unmatched events to a default service
4. Configure service-level rules: PUT /event_orchestrations/services/{service_id} with rules that can set severity, priority, suppress, suspend, or run automation actions
5. Send test events to https://events.pagerduty.com/v2/enqueue using the orchestration's routing_key to validate routing behavior
6. Migrate from deprecated Rulesets: as of January 31 2025, Rulesets are no longer visible in the PagerDuty web app; API access still works but new routing logic should use Event Orchestrations