Event Orchestration

Every event that reaches PagerDuty needs to end up in the right place, with the right context, and sometimes with an automated fix already underway — but hand-managing that logic across dozens of monitoring tools and services quickly turns into an unmanageable pile of one-off rules.

Event Orchestration is PagerDuty's decision engine for processing inbound events. It lets teams define rules that enrich, route, suppress, or take automated action on events before they ever become an incident — either globally across every service, or scoped to a single service's own Orchestration.

Global Orchestrations apply actions and routing logic across services, so ITOps, SRE, and NOC teams can normalize event data and standardize automation account-wide before it ever reaches a specific service. Service Orchestrations then apply their own rules to events that have been routed to them, giving individual teams fine-grained control over their own event processing. Event Orchestration replaced the older Global and Service Event Rules (rulesets), which reached end-of-life on January 31, 2025; accounts still on the old rulesets can migrate automatically using Push-Button Rule Migration.

Learn More