StatusCast Integration Guide

StatusCast provides the perfect way to communicate application downtime and scheduled maintenance with your end-users.  However, uptime monitoring services like PagerDuty are great at alerting your team to potential application problems. With StatusCast’s PagerDuty integration, we’ve tied the two workflows together. Integrating your StatusCast application with PagerDuty ‘s monitoring service will drastically reduce the time it takes to create and post incident in StatusCast. Before you set anything up in StatusCast you’ll need to add a new Webhook to your monitor in PagerDuty.The Webhook URL is unique to your StatusCast application, https://[subdomain].statuscast.com/webhook/pagerduty, just replace [subdomain] with the subdomain of your StatusCast. With that URL ready, log into PagerDuty and navigate to the Services section. For any service/monitor that you’d like to connect to StatusCast simply just add the Webhook URL to it.

In PagerDuty

1. If you already have an existing service that you'd like to tie to StatusCast, go to Services → Service Directory and then click on the service name.  If you don't have a service, create a new service by clicking + New Service. 2. Click on the Integrations tab and click the Add or manage extensions link. 3. For the Extension Type select Generic Webhook. Enter in a Name for your webhook. Then, paste the URL that you copied in step 3 above into the Endpoint URL.  Click on the Save button when done.

In StatusCast:

1. Once that has been saved your service/monitor will send StatusCast information when an incident occurs. For all services/monitors that you add this webhook to, note the Service Name as we’ll need that for the final setup. 2. Now log into your administrative portal ([subdomain].statuscast.com/admin), and navigate to the Monitors section. Here you can create new monitors as well as manage any existing ones. 3. Select + New Monitor to begin the setup. From the Choose Provider drop down, select PagerDuty and enter the Alert Name. *As stated above, the Service Name is the display name of your monitor in PagerDuty.  5. Enter the Authored by which defines who is the author of each incident. Like normal incidents a post can only have a single author. The other Incident settings including Type, Affected components, Subject, and Message reflect the same general options you have when creating an incident. For more information on this process please refer to StatusCast’s How do I post a new incident or status article. 6. With the incident settings finished, define the actual workflow of the incident being posted. Notify theses employees – select which employees StatusCast will notify when this type of incident gets created. Please note that you can select multiple employees. Wait time – is the amount of time StatusCast waits before actually creating your incident. This is typically used to buffer out incidents that are quickly resolved, usually in a matter of a few minutes. If your monitoring service already has this built in, then you can set this value to 0 and StatusCast will post the incident when it’s received. Combine alerts – in case your monitoring services sends out multiple requests you can choose to combine them to prevent redundant incidents from being reported. Auto-publish – if selected your incident will be automatically published, which notifies all subscribers. If this option is turned off then your employees will need to activate the post manually, either by logging into StatusCast and activating it within the Dashboard or by simply replying to the notification email. Auto-close – if selected your incident will be closed when your monitoring service sends an update. By selecting this you can also enter a Closing Comment that will be posted.   If you have any questions about this guide or run into any issues during the setup, please contact support@pagerduty.com to troubleshoot.