-
-
Notifications
You must be signed in to change notification settings - Fork 391
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add group-specific integration key for PagerDuty #181
Add group-specific integration key for PagerDuty #181
Conversation
… return the first pagerduty integration in team integrations
Co-authored-by: Chris <twin@twinnation.org>
Co-authored-by: Chris <twin@twinnation.org>
Co-authored-by: Chris <twin@twinnation.org>
Codecov Report
@@ Coverage Diff @@
## master #181 +/- ##
==========================================
- Coverage 87.09% 86.63% -0.47%
==========================================
Files 48 48
Lines 2154 2177 +23
==========================================
+ Hits 1876 1886 +10
- Misses 186 194 +8
- Partials 92 97 +5
Continue to review full report at Codecov.
|
@achrefbensaadVPaccount I made some adjustments in a6bc003 to support future use cases. Namely, See https://github.com/TwinProduction/gatus#configuring-pagerduty-alerts |
Released in v3.2.2 |
What this is doing ?
Provides support for paging multiple teams based on the
group
selector while keeping backward compatibility to the old pagerduty configuration manifestbehavior: