Hello,
We're excited to announce the implementation of multiple
PagerDuty integrations in Site24x7. With the all new integration
workflow, you can create multiple PagerDuty integrations in your
Site24x7 account via separate PagerDuty Integration keys. It enables
Site24x7 to invoke different incident workflows in PagerDuty for a
unique set of monitor events.
What can you achieve with this all new integration workflow?
PagerDuty is an advanced alerts management tool that offers IT
alerting, on-call scheduling, incident management, and escalation
policies to rectify issues in your IT resources. Previously,
Site24x7's integration with PagerDuty only had a single service
key support; hence, a single integration was possible. With this new
integration workflow, you can create multiple integrations and
streamline incident management within teams by pushing multiple
Site24x7 alarms to same or different PagerDuty accounts. It lets you
setup different escalation policies in PagerDuty and notify your
relevant user groups in case of monitor outage. In a nutshell, you can
have more control over how, when, and who receives Site24x7 alarms in PagerDuty.
Setting up multiple PagerDuty integrations.
We'd advise you to read our help
documentation to learn more about the configuration settings.
Regards,
Abhiram
Excited about the feature.. unfortunately the release broke our automations and several of our monitors (removing them from alerting in pagerduty at all.) I have a ticket open with support #347093 as I still am not 100% sure that I have the updated API information and the API docs have not been updated.
It would be nice if users were alerted PRIOR to a release about changes that are coming in the release and any actions they need to take (such as updating any API calls they are making through automation.)
Any user of pagerduty integration prior to this release should check their monitors to ensure they are still setup to alert through the NEW "third_party_integration" setting rather than "notify_pagerduty" setting.
Hi Damian,
We are extremely sorry for the trouble. We try to provide backward compatibility, unfortunately in some cases we could not. We would devise a plan for deprecating apis in a better way. Until then, we would communicate in advance by making announcement in this community, if there is going to be any breaking changes.
Thillai.