Event Rules is scheduled to end-of-life (EOL) in 2024. 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.
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.
You have several migration options, which are detailed below.
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:
- 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.
- Next, navigate to Services Service Directory and select the service that you want to migrate integration keys for.
- Select the Settings tab and scroll to the Event Management section.
- Click Switch to Service Orchestrations.
- Once this button is clicked, all events that reach the service will be evaluated against the Event Orchestration rules that have been created.
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.
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.
- Once you have created the Global Orchestration and rules described above, navigate to the orchestration and select Integrations.
- Click New Integration and select Permanently migrate integration from existing Ruleset from the dropdown.
- In the modal that appears, select the Ruleset with the integration key that you would like to migrate.
- 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.
- You should see a success message at the top of the screen confirming that the Ruleset has migrated.
For users who do not want to manually re-create their event rules in Event Orchestration, we support the ability to automatically migrate an account's event rules to Event Orchestration rules. This automated migration identically re-creates your existing 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.
Push-button migration is currently available at the service level. A similar feature for global event rules is planned for calendar year 2024.
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, Digital Operations, Event Intelligence, or Customer Service Digital Operations.
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:
- In the web app, navigate to Services Service Directory and select your preferred service.
- Select the Settings tab scroll to the section click View Basic Service Event Rules.
- Click Convert to Orchestration, and, in the modal window, confirm the action by clicking Convert to Orchestration again.
- Optional: Click View the Orchestration to navigate directly to the converted Service Orchestration
- 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.
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.
On the EOL date, a button in the web app will be displayed next to all event rulesets that still exist. The button will allow you to automatically copy those rules into Event Orchestration rules. You will also be able to migrate a ruleset using the API. While this does not take advantage of the event rule compression capabilities of Event Orchestration, this will preserve all existing event rule functionality.
Your event rules will continue to exist in a read-only state in PagerDuty. During this time they will continue to work normally and your event processing will not be impacted. However, you will not be able to create new event rules or edit existing ones. Additionally, we will no longer formally support event rules, which means bugs will not be addressed and new features will not be made backwards compatible with event rules.
You will be able to migrate your event rules to Event Orchestration via the API or a button in the web app, however you will not be obligated to do so. If you choose not to migrate your event rules before the end of life date, please understand that event rules will become unsupported and PagerDuty will not maintain backwards compatibility with any new features that are released for Event Orchestration. This means that migrating event rulesets to Event Orchestration after the deadline increases the likelihood that we will not be able to identically mirror the original behavior from event rules.
Event Orchestration is a direct upgrade from Event Rules. Basic Event Orchestrations can perform all the same basic event processing actions that event rules can perform with the added benefits of improved UI, better rule creation, APIs and Terraform support, and advanced conditions. For customers with the PagerDuty AIOps add-on or Digital Operations plans, Advanced Event Orchestrations bring even more functionality to the table, including contextual conditions, webhooks, paused incident notifications, rule nesting, and a direct integration with Automation Actions.
Below are a few of the key ways that Event Orchestration is superior to Event Rules:
- Easier to use: Architecturally, Event Orchestration takes advantage of PagerDuty’s more modern approach to front-end development by leveraging React as its core frontend stack. This allows customers to navigate their rules with less lag and greater support for accessibility improvements in the future.
- More complex event processing: Because of the condition language that Event Orchestration supports and the capability to nest rules, customers using Event Orchestration can perform complex event processing actions with a fraction of the configuration effort. What could once be accomplished with 10 event rules can now be done with 1 Event Orchestration rule.
- More robust support for automation: Users can trigger webhooks with custom headers or automation actions.
- More precise event processing: Rule nesting allows users to execute automations with a high degree of precision as customers can itemize out in detail each known failure start for their systems, deploying automation to each with confidence.
We highly recommend using the Service Integration Key, REST API or Global Integration Key migration methods listed above to migrate to Event Orchestration. That said, users will have access to an automated rule migration tool later this year. This tool will automatically copy all existing event rules into Event Orchestration rules on a per ruleset basis, initiated by a user either by an in-product button or API.
After the EOL date, event rules will continue to process events in a read-only state, however we will no longer formally support the feature.
Is Event Orchestration going to be a true replacement for Event Rules, or will I be losing functionality?
Event Orchestration has the same features as Event Rules with the added benefit of being built on a more sustainable front-end framework. The backend for Event Orchestration is identical to the backend for Event Rules, allowing Event Orchestration to benefit from the years of testing that has been done with Event Rules. This shared backend also means that the processing outcomes for events sent to Event Orchestration will be identical to Event Rules, with the added benefit of having easier-to-understand rules.
There is support available from the Professional Services team for customers who need it. If you are interested in this, please contact your account team and they can help set this up.
If you have additional questions, please reach out to the Support team or your Customer Success representative.
Updated 4 months ago