[pagerduty] send full event payload on resolve #2472
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asvinours
changed the title
docmerlin
approved these changes
Feb 4, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required for all non-trivial PRs
Description
Pagerduty made Ruleset feature (https://support.pagerduty.com/docs/rulesets) available to everyone couple of months back.
The issue is that
triggerandresolveevents need to be routed to the same service when rulesets are used.Because the resolve event only contains a subset of the trigger payload, it's very complicated to do proper routing.
Pagerduty is accepting the full payload on resolve just fine (I tested it with our infrastructure) and the extra keys in the payload allows proper routing.