Migrate to Event Orchestration

Migrate in preparation for Event Rules' upcoming EOL

Event Rules End-of-Life

PagerDuty has decided to end-of-life Event Rules on April 30, 2023. We have made this decision to ensure that we are dedicating our resources toward building the most robust and reliable event-driven enrichment and automation experience for our customers. Event Orchestration was released earlier this year as the next evolution of Event Rules, and it is now the best way for users to compress rule volumes, improve noise reduction, and more effectively automate away well-understood manual work.

We have plenty of migration paths to support this end-of-life (EOL). Additionally, on the EOL date, we will auto-migrate any remaining event rules you are using to Event Orchestrations, one-to-one. From then on, you’ll be able to do everything in Event Orchestration that you can in Event Rules today. Event Orchestration has the same features as Event Rules and it uses the same backend architecture, ensuring that event processing has billions-of-events-worth of testing already baked in.

👍

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

There are several migration options already available today, with more on the way in the coming months. Below is a summary of current and planned migration options.

Service Integration Key Migration

👍

Available Now

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

👍

Available Now

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.

Global Integration Key Migration (Early Access)

📘

In Development

Early Access is scheduled to begin in late October 2022.

Global Integration Key migration will allow 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.

Automated Rule Migration

📘

In Development

Planned availability in April 2023.

🚧

Recommendation

We recommend using other forms of migration (above) instead of using Automated Rule Migration, as it is a best practice not to 'lift and shift' rules to Event Orchestration. Event Orchestration's conditional language allows for simplified, yet powerful evaluations that can reduce maintenance costs and speed up rules processing.

For users who do not want to manually re-create their event rules in Event Orchestration, we will support the ability to automatically migrate an account's event rules to Event Orchestration rules. This automated migration will identically re-create your existing rules, retaining the same behavior and outcomes of event processing in Event Orchestration without you or your teams having to spend any time or resources.

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.

FAQ

What will happen to my event rules?

Expand

At the EOL date, all event rules that still exist will be auto-migrated as identical Event Orchestration rules, one-to-one. 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 for three months after EOL. 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. After this three-month period, Event Rules will be fully removed from the PagerDuty product.

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

Expand

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 Event Intelligence 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.

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

Expand

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 without users having to do any work.

Any users who do not wish to re-create their event rules will have their rules automatically migrated to Event Orchestration on January 31, 2023. These rules will be created, but will not have event traffic sent to them until Event Rules is fully removed from the PagerDuty product in April 2023.

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

Expand

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.

Is PagerDuty able to provide more support for my migration?

Expand

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.

Where can I learn more about Event Orchestration?

Expand

Please read our Event Orchestration article for more information. PagerDuty University also has some great trainings, including:

Who can I contact if I have more questions?

Expand

If you have additional questions, please reach out to the Support team or your Customer Success representative.