Migrate to Event Orchestration

Event Rules webpages reached end-of-life (EOL) on January 31, 2025. PagerDuty made this decision to ensure that it dedicates resources toward building the most robust and reliable event-driven enrichment and automation experience for customers. Event Orchestration, the evolution of Event Rules, is currently available and is the best way for you to compress rule volumes, improve noise reduction, and more effectively automate well-understood, manual work. Event Orchestration has the same features as Event Rules and it uses the same, heavily tested backend architecture.

Migration Options

You have several migration options, which are detailed below:

• Service Integration Key Migration
• REST API Migration
• Global Integration Key Migration
• Push-Button Rule Migration

Service Integration Key Migration

With Service Integration Key migration, you can direct your events towards existing Service Orchestration rules without having to change or update integration keys. No architecture is changed in this switch, so you do not need to change any integrations to PagerDuty. All of your events sent to a service will automatically start flowing through to Event Orchestration instead of Event Rules.

To migrate your service integration keys:

1. Before performing this migration, it is recommended that you create Event Orchestration rules for the service. If no Service Event Orchestration exists, then the default behavior is for events to trigger their event action as they normally would.
2. Next, in the PagerDuty web app navigate to Services Service Directory and select the service that you want to migrate integration keys for.
3. Select the Settings tab and scroll to the Event Management section.
4. Click Switch to Service Orchestrations.
5. Once this button is clicked, all events that reach the service are evaluated against the Event Orchestration rules that have been created.

REST API Migration

Event Orchestration has a new set of APIs that allow you to nest rules together. To migrate existing APIs over to the new REST APIs, you can leverage the new Event Orchestration Terraform Provider to create large volumes of Event Orchestration rules rapidly. Professional services are available to help you with this process.

Information on the new REST APIs can be found in the Developer Documentation, and information on the Event Orchestration Terraform Provider can be found in Terraform's documentation. To help get you started, here are a few endpoints you may find useful:

• List Global Rulesets
• List Service Event Rules
• Create an Event Orchestration
• Create an Integration
• Migrate an Integration to a New Orchestration
• Update a Global Orchestration
• Update a Service Orchestration

Global Integration Key Migration

Global Integration Key migration allows you to retain your existing integration keys and have them evaluate against Event Orchestration rules instead of a Global Event Ruleset. The backend architecture for Event Orchestration is identical to Global Event Rules, so no ingestion or processing behavior changes. Events are simply evaluated against Event Orchestration rules instead of event rules.

To migrate your global integration keys:

1. Once you have created the Global Orchestration and rules described above, navigate to the orchestration in the PagerDuty web app and select Integrations.
2. Click New Integration and select Permanently migrate integration from existing Ruleset from the dropdown.
3. In the modal that appears, select the Ruleset with the integration key that you would like to migrate.
4. Note that migration is immediate. Once you click Migrate, the Global Ruleset will become inactive. When you are sure that you would like to move forward, click Migrate.
   1. You should see a success message at the top of the screen confirming that the Ruleset has migrated.

Push-Button Rule Migration

If you do not want to manually re-create your service event rules in Event Orchestration, PagerDuty supports the ability to automatically migrate an account's service event rules to Event Orchestration rules. This automated migration identically re-creates your existing service event rules, retaining the same behavior and event processing outcomes in Event Orchestration. You can trigger this migration on a per-ruleset basis via the API.

Migrate Service Event Rules to Service Event Orchestration

The Push-Button Rule Migration feature leverages the API to allow you to automatically convert your Service Event Rules into Service Orchestration Rules. Read Convert a Service's Event Rules into Event Orchestration Rules in the developer docs for more information.

All functionality from the migrated Service Event Rules is supported in Service Event Orchestration, except in cases where the rule contains an unsupported exception. Refer to the provided exception documentation for details.

If a service's Service Event Rules have more than 25 rules, rule nesting is used to accommodate additional rules under Service Event Orchestration.

Note that this nesting is only supported to extend the number of Service Orchestration Rules on a service. Further nesting is not supported unless the account has purchased AIOps, Enterprise for Incident Management, Digital Operations (Legacy), Event Intelligence, or Enterprise for Customer Service.

To migrate Service Event Rules to Service Event Orchestration:

1. In the PagerDuty web app, navigate to Services Service Directory and select your preferred service. Locate the service's ID in the page's URL.
2. Use the Convert a Service's Event Rules into Event Orchestration Rules endpoint to migrate the service's rules.

Terraform

If you have configured your event rules using Terraform, version 2.5.0 of the PagerDuty Terraform provider introduced support for Event Orchestration resources that can help you reproduce event rules using Event Orchestration rules instead. To reproduce Service Event Rules you will want to use the pagerduty_event_orchestration_service resource. To reproduce a Global Ruleset you will want to use the pagerduty_event_orchestration, pagerduty_event_orchestration_global, and pagerduty_event_orchestration_router resources.

Global Event Rules Migration Guidance

Event Orchestration can identically replicate the features and functionality of Global Event Rules without requiring Global Orchestrations.

To effectively migrate your Global Event Rules to Event Orchestration PagerDuty suggests the following:

1. Create a new Event Orchestration.
2. Create a routing rule for each service that appears in the Global Event Ruleset you are migrating.
3. For each service from step two, create Event Orchestration rules that replicate the actions (i.e., setting incident priority) from the corresponding Global Event Ruleset.
4. Once you have replicated the rules and actions, navigate to the Integrations section of the Event Orchestration you created and click New Integration.
5. From the options presented, select Permanently migrate integration from existing Ruleset and select the Global Event Ruleset you are migrating from the dropdown. This transfers the integration key to the new Event Orchestration. No data will be lost as part of this process and events immediately start using the new Event Orchestration rules you created.

FAQ