Skip to main content

Back in 2021 I created new services with Global Event rules to replace the services with email integrations. Now with the new Event Orchestration coming I need to convert them. But for the life of me I cannot find my Global Event rules. It’s been that long since I had to change anything in PD so I am rusty. Want to get them converted before Jan.

Any help would be greatly appreciated.

Thank you,

 

Vito.

 

Can I delete this? Found what I was looking for.


Hi ​@Vito, happy to know you found your legacy Global Event rules. Feel free to come back to this thread and post how did you get to it - that can help other community members that are facing the same thing!

Here's a helpful resource for folks going on the same path:
 

📚 Global Event Rules Migration Guidance

 


@xamici thank you for your reply. I had some success on my first Event Orchestration. I created a test service to use on just me in the escalation rule. I sent the email and the incident an incident was created and I got the push on my Pager Duty app.

Currently in my Global event rules I have 3 conditions.

  1. headers.subject contains <my subject text>
  2. Body Contains <My first condition partial match>
  3. Body Contains <My second condition partial match>

In the Event Orchestration under Service Routes I figured by trial and error that “event.dedup_key” is looking at the subject line of the email. I tried also using it for the body but that didn’t trigger an incident. The body of the email contains the other conditions I need to either trigger the event or not trigger the event. What do I use to find text in the body of the email?

Thanks in advance.


@Vito, do you have a link to the specific rule that is not working as expected?

It could be related to how the email is ingested or could just be a misunderstanding of how the orchestration rules work.

We also have this Knowledge Base article that might help you with building the rules: https://support.pagerduty.com/main/docs/event-orchestration-examples#if-events-match-certain-conditions
 

The email subject will be used as a default deduplication key. In other words, emails with the same subject line will automatically be deduplicated. To change this behavior, add a custom deduplication key with an orchestration rule action.


@xamici It could be a misunderstanding of how they work. Seems I am confused with Service Route and Service Orchestration. I’ll read the support article and see if I can figure it out.

Also, the link you asked for is that the kink in Intergration tab?


@Vito, yes, the link to the orchestration should be fine 😊

 


@xamici where would I find that link you need?


@xamici OK I figured what I was doing wrong with Service Route event rule. I was not including the field. So my conditions looked like this

event.custom_details. matches part 'SVR12D = Primary Server' and

event.custom_details. matches part 'Unplanned Switchover'

So I corrected that part so it is now

event.custom_details.subject matches part 'SVR12D = Primary Server' and

event.custom_details.body matches part 'Unplanned Switchover'

So I think I am halfway there now trying to figure out how, if I need to, set up Service Orchestration.


Reply