---
title: PagerDuty
slug: pagerduty
docTags: 
createdAt: 2022-07-01T05:23:49.000Z
---

# Purpose

Echoes can connect to your PagerDuty Services and monitor your incidents lifecycle in order to produce some metrics such as the [Mean time to recovery](docId\:lGfIZtDECxM2tQ2KurlIp).

# Installation

PagerDuty integration is done through the [integrations settings](https://app.echoeshq.com/admin/integrations). The installation will guide you into generating a [PagerDuty API token](https://support.pagerduty.com/docs/api-access-keys#rest-api-keys) and installing the webhooks.

::Image[]{src="https://api.archbee.com/api/optimize/cnN9HGi_h1eJLSFAvJkF4/IMna4YVdZvP_6JkJhSppE_cleanshot-2022-07-06-at-0705522x.png" size="80" width="1584" height="946" caption="PagerDuty installation" position="center" showCaption="true"}

## Required permissions

The following permissions are required for Echoes to interact with PagerDuty:

- **Read access** on [Services](https://support.pagerduty.com/docs/services-and-integrations) and [Incidents](https://support.pagerduty.com/docs/incidents).
- **Write acess** in order to create and configure [webhook subscriptions](https://support.pagerduty.com/docs/webhooks#add-a-v3-webhook-subscription) so that Echoes can receive events for a given service.

This makes the **Stakeholder** user role or a **Restricted Access role with the Manager team role** the minimum permissions required.