Event Rules End-of-Life

Event Ruleswebpages are scheduled to end-of-life (EOL) on January 31, 2025. We made this decision to ensure that we dedicate our resources toward building the most robust and reliable event-driven enrichment and automation experience for our customers. Event Orchestration, the evolution of Event Rules, is currently available and is the best way for users 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.

👍

Recommendation

We highly recommend that you migrate to Event Orchestration as soon as possible so you can take advantage of the new functionality, such as improved UI, rule creation, APIs and Terraform support, advanced conditions, and rule nesting.

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, 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 will be 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 our 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 interested users with this process.

Information on the new REST APIs can be found in our 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 users to retain their 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 will change. Events will simply be evaluated against Event Orchestration rules instead of event rules.

To migrate your global integration keys:

🚧

Before You Start

If you have not already done so, please perform the following before migrating keys:

• Create a Global Orchestration
• Ensure that you have created routing rules and global or service orchestration rules that replicate any routing settings and event modifications that you'd like to keep.

If you do not replicate routing rules, events will no longer reach the appropriate services, and if you do not replicate the event modifications, actions will be lost.

1. Once you have created the Global Orchestration and rules described above, navigate to the orchestration 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. Please 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

For users who do not want to manually re-create their service event rules in Event Orchestration, we support 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 or by pushing a button in the PagerDuty web app.

Migrate Service Event Rules to Service Event Orchestration

The Push-Button Rule Migration feature includes a button on the Service Event Rules page that allows customers to automatically replicate their Service Event Rules into Service Orchestration Rules.

The migration process involves the following steps:

• When you trigger Push-Button Migration, Service Event Rules will be replicated as Service Event Orchestration rules on the selected service.
• The newly created Service Event Orchestration rules will follow the same order as the rules listed under Service Event Rules.
• All functionality from the migrated Service Event Rules will be supported in Service Event Orchestration, except in cases where the rule contains an unsupported exception. Please refer to the provided exception documentation for details.

Once the migration is initiated, Service Event Rules will switch to read-only mode and can no longer be edited. If a service's Service Event Rules have more than 25 rules, rule nesting will be used to accommodate additional rules under Service Event Orchestration.

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

🚧

Enable Service Event Orchestration

The migration process will not automatically enable Service Event Orchestration. This means that, while Service Orchestrations may be configured, they will not used to process incoming events unless you have enabled Service Orchestrations on the service's Settings page. Enabling Service Orchestrations on a service is covered in step five below.

To migrate Service Event Rules to Service Event Orchestration:

1. In the web app, navigate to Services Service Directory and select your preferred service.
2. Select the Settings tab scroll to the section click View Basic Service Event Rules.
3. Click Convert to Orchestration, and, in the modal window, confirm the action by clicking Convert to Orchestration again.

4. Optional: Click View the Orchestration to navigate directly to the converted Service Orchestration

5. In order to enable the newly created Service Event Orchestration rules, so that they are applied when the service receives an event, please follow the instructions to enable service orchestration on the service.

📘

Migrate via REST API

You can also migrate from Service Event Rules to Service Event Orchestration using our REST API. Please read Convert a Service's Event Rules into Event Orchestration Rules in our developer docs for more information.

Terraform

If you’ve 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’ll want to use the event_orchestration_service resource. To reproduce a Global Ruleset you’ll want to use the event_orchestration, event_orchestration_global, and 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 we suggest 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, etc.) 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 will transfer the integration key to the new Event Orchestration. No data will be lost as part of this process and events will immediately start using the new Event Orchestration rules you created.

📘

Event Evaluation Order

Global Event Rules are not evaluated before events are routed to services, whereas Global Event Orchestration rules are. This change in behavior allows Global Event Orchestration to reduce the number of required rules and improves downstream routing logic.

FAQ

What will happen to my Event Rules?

What happens if I don’t migrate my Event Rules?

What’s the difference between Event Rules and Event Orchestration?

Do I have to create all my event rules again in Event Orchestration?

Is Event Orchestration going to be a true replacement for Event Rules, or will I be losing functionality?

Is PagerDuty able to provide more support for my migration?

Where can I learn more about Event Orchestration?

Who can I contact if I have more questions?