Go to All Forums

Multiple PagerDuty service keys

We use site24x7 to monitor several services which are managed by different teams, with different escalation policies on PagerDuty, but as only 1 service key is currently supported we cannot have different service alerts go to those different teams / policies.
Like (5) Reply
Replies (13)

Hi,

Thanks for bringing in this request related to multiple PagerDuty service keys.

We have added this to the roadmap and will keep you posted once we start working on the same. Meanwhile, we were curious to know if you are one among the MSP's and if you are using Site24x7 to manage your clients. Please brief us more about your requirement and we shall take it further based on the feasibility.

Regards,
Sushma.
Like (0) Reply

No we're just a single department in a single organisation but with multiple (partially overlapping) teams managing different live and staging services.
Like (0) Reply

I think we are interested in the same feature, but perhaps for different reasons. Here's our setup...

We have several health check endpoints on an internal site. We want to alert our team through PagerDuty whenever one of these endpoints/services is unhealthy, with a message related to which endpoint/service is unhealthy.

If our site is down, we want one type of alert. However, if one of our datastores has become unhealthy, we want a different kind of alert.
Like (0) Reply

We would also like to see this feature added.


Our use case would be, we want different monitors to be able to trigger different pagerduty workflows, such as one alarm to pagerduty always triggers the workflow to ring an engineer regardless of hour, another alarm would go to a pagerduty workflow that only creates high priority incidents during business hours but low priority incidents after hours.

Like (0) Reply

Hello All,

Thanks for adding your Pagerduty related enhancement requests to this thread.

We did list out the requirements to our product team, however, they are yet to get started with the action items since they have some more priority based enhancements being worked upon right now.

We shall keep you posted once we start supporting the Pagerduty requests.

Regards,
Sushma.
Like (0) Reply

by jlam
This is exactly the feature I was hoping to have.  We have different teams to handle different services.  Currently I'm setting up using emails to handle the functionality; it is not the ideal solution.

+1 for this feature request.
Like (0) Reply

by Ke
We are evaluating switching to Site24x7 from another provider, and the lack of this feature is a deal breaker.  We'll keep our eyes here for a while and hopefully we can continue our evaluation in the near future.
Like (0) Reply

Adding to this.

Our use case is that we have multiple products that we monitor and there are engineers specialized in each. We need to alert the appropriate team specialized in the product. Today's work around is that we have to create a user and do email integrations to pagerduty for any additional product. 
Like (0) Reply

Hi,

This is a long pending feature to be supported.  We have a base framework already done to support multiple integrations on third party.  We may need to move our Pager Duty support over this framework and migrate the existing users on this.

We have prioritized this and will be taking this up in our next milestone. It will take 4-8 weeks to complete this activity.

Will keep you updated here once it is done.

Raghavan
Like (0) Reply

This is a much needed feature for us as well.  We have worked around it for the time being by creating multiple services in pager duty and multiple alert contacts in the users areas.  Each alert contact reaches out to a different pager duty service.  
Like (0) Reply

Hello,

As the popularity grows on this feature request, we have already started working on to support multiple Pager Duty integration in Site24x7. This will list the pager duty integrations in monitor form and allow users to choose the required integration to be invoked on any events for the monitor.

Will keep posted on once the feature is released.

 

Raghavan

Like (0) Reply

We have a similar requirement, with multiple application teams that have different pagerduty services for alerting. We're eagerly anticipating the release of this feature. 
Like (0) Reply

Hello,

We're excited to announce the implementation of multiple PagerDuty integrations in Site24x7. With the all new workflow, you can now 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.

How to set-up this integration?

We'd advise you to read our help documentation to learn more about the configuration settings.

Regards,

Abhiram

Like (0) Reply
Was this post helpful?

Statistics

13 Replies
9106 Views
0 Followers

Tags