PagerDuty

Split + PagerDuty is a community-supported integration. Community-supported integrations are not owned or maintained by the engineering teams at Split or PagerDuty. We do our best to ensure that we share only high-quality community integrations and solutions, but we do not work on these projects directly, nor can we guarantee that they’re consistently maintained.

To learn more about all our integrations, check out our integrations page. If you’d like a demo of Split or help to implement any of our integrations, contact support@split.io.

Split + PagerDuty

PagerDuty is a leading provider of on-call management, incident response, and event intelligence. Split is uniquely suited to detect degradations in key metrics when features are rolled out. Configuring alerts in Split, you can be notified when a rollout impacts the metrics your team cares about.

Split sends alerts on degradation via email. PagerDuty can receive these emails and feed them into its modern incident response engine to be distributed for action as appropriate. The integration uses out-of-the-box features of both products.

Prerequisites

• PagerDuty
• Split platform edition with Split's monitoring pack

How to Use

PagerDuty: Locate the Incoming Event Source

From PagerDuty’s main menu, go to Configuration and Event Rules.

Select the Default Global Ruleset or one of your choosing.

Open the Incoming Event Source to find a screen like the one shown above. A unique integration key and accompanying email address is shown. This is the email address you will use with the Split Alert Policy. Copy the email address and save it for use later.

PagerDuty: Create a Rule

Create a new rule to process the email alerts from Split. The rule can be simple. In the screenshot above,

• From address is “noreply@split.io”
• Subject contains “Split Alert Fired”

Save the rule.

The actions performed by my rule are to route to an appropriate service -- “AB feature testing” -- set the severity to critical, label the incident with a note that “Split has detected a degradation in a key metric”. You can specify whatever action you think is most appropriate; PagerDuty is incredibly flexible in its response to the alerts.

Split: Configure a Metric Alert Policy in Split

Select a metric on which you would like to alert. The full details on configuring an alert policy are found in the Split's documentation.

Take the email address you saved from PagerDuty containing your unique key, and paste it in as additional email. Save the changes.

You are now ready for your alert to fire to PagerDuty.

Split: Trigger an Alert

Split does not have a test button to trigger an alert. The simplest approach is to write a test program that generates fake users to create impressions and events that will trigger an alert. Contact the contributor David Martin for help and suggestions.

PagerDuty: Handle a Split Incident

If the integration has been configured properly, a new alert email from Split will appear as incidents in PagerDuty, per your rules configuration.

The full detail of the email message is also available in PagerDuty by drilling into the incident.

In this case, the test_split degraded the processing time by 30%.

You have successfully integrated Split alerts with PagerDuty.

If you have questions or comments, contact the contributor David Martin.