> For the complete documentation index, see [llms.txt](https://docs.secoda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.secoda.co/extensions/pager-duty.md).

# PagerDuty

## Getting Started

To integrate PagerDuty with Secoda, follow these steps:

1. **Create a new Service in PagerDuty (Optional)**
2. **Create an "Events API v2" Integration**
3. **Connect the Integration with Secoda**

### Step 1: Create a New Service in PagerDuty (Optional)

If you already have a service you want to use, you can skip this step.

To create a new service in PagerDuty:

1. Log in to PagerDuty.
2. Click the "Services" tab.
3. Click "New Service".
4. Provide a name, set an escalation policy, and assign it to team members.
5. If prompted, create an integration using "Events API v2".

### Step 2: Create an "Events API v2" Integration

If you already created an "Events API v2" integration during the service creation, you can skip this step.

To create a new integration:

1. Log in to PagerDuty.
2. Click the "Services" tab.
3. Select the service you want to integrate with Secoda.
4. Click the "Integrations" section on the service page.
5. Click "Add Integration" or "Add another integration".
6. Select "Events API v2" and add it to your service.

### Step 3: Connect the Integration with Secoda

1. Go to your service and open the "Integrations" section.
2. Open the "Events API v2" section.
3. Copy the Integration Key from the configuration section.

### Post-Integration Steps

After connecting PagerDuty to Secoda:

1. Open the "Alerts" section in the integration configuration.
2. Enable "Alert on incidents from Secoda Monitors" to receive monitoring incidents.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.secoda.co/extensions/pager-duty.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.