PagerDuty Integration

PagerDuty + pganalyze Integration Benefits

• Notify on-call responders based on alerts sent from pganalyze
• Link PagerDuty incidents to issue details in pganalyze
• Automatically acknowledge PagerDuty incidents when issues are acknowledged in pganalyze
• Automatically resolve PagerDuty incidents when pganalyze detects an issue has been resolved

How it Works

In order to ensure your database is running smoothly, pganalyze runs a number of checks every time it receives statistics snapshots about your database from the Collector. These checks can create issues in pganalyze, which you can view by navigating to the Alerts & Check-Up page in the left menu in pganalyze. Once the underlying problem has been resolved, pganalyze will automatically resolve the issue.

Integration with PagerDuty can trigger incidents on a PagerDuty service when new critical issues are created (or when existing issues escalate to critical severity). Once a pganalyze issue has been resolved, the associated PagerDuty incident will be automatically resolved as well.

Requirements

In order to set up the integration with PagerDuty, and to manage the alert destinations and rules that route issues to it, you will need modify permissions on the pganalyze organization.

Support

If you need help with this integration, please contact support@pganalyze.com.

Integration Walkthrough

Follow these instructions for your selected organization in pganalyze.

Initial setup

Before configuring alerts, you will need to connect your pganalyze organization to PagerDuty:

1. In the top menu, click the x in the Server dropdown if a server is selected to clear the active server
2. In the left menu, click the Settings item
3. On the organization settings page, click the Integrations tab
4. In the panel labeled PagerDuty, click the Connect to PagerDuty button
5. Continue to authenticate with PagerDuty and select which services you would like to connect to pganalyze
   • Services you select will later be available to configure for alerting; no alerting is enabled by default
6. Once connected, select a service from the dropdown and click Test integration to trigger a test alert to the selected service and verify that the integration is configured correctly

Configuring alerts

Once PagerDuty is connected, route issues to it using an alert destination and an alert rule:

1. In the left menu, click the Alerts & Check-Up item
2. On the Alert Destinations tab, click Add destination (or edit an existing one)
3. Give the destination a name and add a PagerDuty target, selecting the service to alert
4. Save the destination
5. On the Alert Rules tab, create a rule that selects the checks you want to alert on and routes to this destination. Leave the server unset to apply the rule to all servers, or select a specific server.

pganalyze will trigger an incident on the selected service the next time a matching issue reaches critical severity. Only critical issues are sent to PagerDuty.

Note: If you stop routing a check to PagerDuty while there are open incidents, you will need to resolve those incidents manually.

Uninstalling the integration

1. In the top menu, click the x in the server dropdown if a server is selected to clear the active server
2. In the left menu, click the Settings item
3. On the organization settings page, click the Integrations tab
4. In the panel labeled PagerDuty, click the Reset integration button
5. You should see “Success! Reset complete!” and the integration will be removed

Note: If you uninstall the PagerDuty integration while there are open incidents, you will need to resolve these incidents manually.

Resetting the integration

If you would like to change the PagerDuty services you connect with pganalyze, go through the uninstall steps and the initial setup steps. Your alerting configuration will be maintained. If your alerting configuration references channels that no longer exist, you will need to update these manually or contact support@pganalyze.com.