Overview Retrieves the router configuration for a specific event orchestration. The router determines how incoming events are routed to different services based on matching rules.
This is a read-only tool that queries your PagerDuty account without making any changes.
Parameters The ID of the event orchestration to retrieve router configuration for
Response Returns an EventOrchestrationRouter object:
The orchestration router path configuration Show EventOrchestrationPath properties
Always “router” (indicates this is a router-type set of rules)
Reference to the parent Global Event Orchestration (read-only) Always “event_orchestration_reference”
API URL for the parent orchestration
API URL for this router configuration (read-only)
The router contains a single set of rules (the “start” set). Events are evaluated against these rules in order, and routed to a service based on the first matching rule. Maximum length: 1. Show EventOrchestrationRuleSet properties
ID of this rule set. For routers, this is typically “start”.
List of routing rules Show EventOrchestrationRule properties
Description of the rule’s purpose
Conditions to match. The rule matches if ANY condition matches. Show EventOrchestrationRuleCondition properties
PCL condition string (e.g., “event.summary matches part ‘my service error’”)
actions
EventOrchestrationRuleActions
Actions to take when this rule matches Service ID to route the event to (e.g., “PSI2I2O”)
Dynamically route based on event payload contents (AIOps customers only)
Whether this rule is disabled
catch_all
EventOrchestrationCatchAll
Actions to take when no rules match actions
EventOrchestrationRuleActions
Default routing actions
Creation timestamp (read-only)
User who created this configuration (read-only)
Last update timestamp (read-only)
User who last updated this configuration (read-only)
Version of these orchestration rules (read-only)
Usage Examples Get router configuration Show me the router configuration for orchestration P1A2B3C
View routing rules What routing rules are configured for orchestration P1A2B3C?
Check catch-all behavior Where do unmatched events go for orchestration P1A2B3C?