Connectors – PagerDuty

API Fortress + PagerDuty Integration Benefits:

  • Notify on-call responders based on failures in your API Fortress tests.
  • Send critical information on the failure as well as a link to the test report from the failed test.
  • Create high and low urgency incidents based on the severity of the failure via dynamic tags in the test.
Below is a quick guide to setting up and using the PagerDuty connector.

Note: this connector does not come pre-loaded out of the box, and will need to be loaded separately. To learn how to load the connector into your API Fortress instance click here.

This connector is built and supported by API Fortress. If you need any help with this connector please reach out to API Fortress support at support@apifortress.com.

  1. Go to settings page
  2. Click on “Alert Groups”
  3. Create a new group or add a connector to an existing alert group
  4. Add a new connector
  5. Choose the PagerDuty connector
  6. Configure the connector
    1. routing_key is the integration key generated for a service in PagerDuty. The routing_key can be generated as such:
      1. click on the service you would like to alert, and click on the “Integrations tab”
      2. Use an existing integration or create a new one specifically for API Fortress. The integration key provided is the “routing_key”
    2. severity is the level the alert should be sent as. (critical, error, warning, and info)

    3. dedup_key is a key that will allow to you match a triggered alert with a response for that alert

    4. event_action is the action you would like the alert to take. (trigger, acknowledge, and resolve)

  7. Go into project settings for a project you would like PagerDuty alerts set up for
  8. Add the alert group that contains your PagerDuty connector to this project