De-duplication through event V2 API

@AuroreW wrote:

Hello,

I am integrating PagerDuty with our current alerting system.
To create a new incident, I am using the V2 event API as described here : https://v2.developer.pagerduty.com/docs/trigger-events

However I am running into some issues with the de-duplication.
When I trigger the first incident, I assign it an incident key and it is showing correctly in PagerDuty interface.
However, if I trigger another incident (as we fire alert every X minutes) with the same incident key, the REST call give me back a 200 response but the second incident is not showing in the PagerDuty interface.
I would have assumed the second incident show the same way than when two incidents are merged (ie one incident, two triggers).

It is easy to re-produce this behaviour by submitting twice the form at the bottom of the documentation : https://v2.developer.pagerduty.com/docs/trigger-events

If anyone could point me out what am I doing wrong or point me out if I completely misunderstood the de-duplication process, I would appreciate.

Regards,

Posts: 1

Participants: 1

Read full topic