StatusHub Integration


PagerDuty is a popular DevOps tool that allows teams to manage resources and communications. StatusHub is built to communicate issues and incidents to your users and customers. Linking these systems lets your technical team take advantage of automation and save time. Their time is even more precious during unexpected incidents; automate the detection and resolution process to solve issues in record time.

About PagerDuty

In an always-on world, teams trust PagerDuty to help them deliver a perfect digital experience to their customers, every time. PagerDuty is the central nervous system for a company’s digital operations. They identify issues and opportunities in real-time and bring together the right people to respond to problems faster and prevent them in the future. From digital disruptors to Fortune 500 companies, over 12,000 businesses rely on PagerDuty to help them continually improve their digital operations—so their teams can spend less time reacting to incidents and more time building for the future.


PagerDuty aggregates data from multiple monitoring tools depending on your setup. When PagerDuty identifies an incident in your system, it will push this notification to your StatusHub account through our secure connection. When StatusHub receives this notification it will then automatically create an incident report and post it to your StatusHub, automating one of the more time-consuming steps in the incident resolution process.

Your technical team now has time to investigate and, ideally, resolve the detected problem quickly with the peace of mind of knowing that your customers and users have been informed.


Technical Overview of PagerDuty Integration with StatusHub

Because PagerDuty integration is done through a URL with a service token, it’s a one-to-many association. A single webhook can’t create incidents in multiple services.

The PagerDuty integration can only create incidents in StatusHub.

A “yellow” StatusHub status is not possible with this integration. Only the “red” and “green” options will be relevant.

The incident title will be “PagerDuty Alert” and, currently, can not be customized.

The incident body will be taken from the “subject” key from “triggersummarydata”, which consists of the incident details. Example body: “CPU Load High on xdbproductionecho.”

Check how StatusHub works for you and your end users!