getsentry / getsentry/sentry

Configure Sentry integration with PagerDuty using API

Open
#101,912 3 comments 0 reactions 0 assignees View on GitHub
Feature Metrics PagerDuty Product Area: Settings - Integrations
Dominant language
Python
Stars
44.8k
Forks
4.9k
Avg merge
22h 21m
Merged PRs (30d)
586

Description

### Problem Statement

I want to configure an existing PagerDuty integration in Sentry to add a new integration key for the service using the REST API.

This feature is essential for providing standardized observability workflows, and creating integrations for hundreds of services manually is not viable.

### Solution Brainstorm

Support team pointed me to a previous request, which was closed as won't do: [https://github.com/getsentry/sentry/issues/99917]()
I understand the manual step in the UI would be hard to implement in the API as it is. It creates the integration in PagerDuty for me. I wanted to take a different approach, create integration in PD using their API, and then provide the integration key to Sentry. Then there's no need to authenticate with PD on the Sentry side, reducing the complexity.

### Product Area

Settings - Integrations

We want to define a set of [lightweight metrics]() that SDKs can automatically collect for e.g. framework, language or platform, focusing only on signals that **do NOT overlap with Tracing**. Ideally these metrics should give a quick sense of app or runtime health, … while deeper investigation will still rely on traces or profiles.

Examples**:**

* Node.js runtime metrics (e.g., event loop delay, heap usage)
* Prisma-related metrics in Next.js
* Mobile CPU / memory usage to help surface potential ANRs or app hangs

---

**Candidate Metrics (add more below)**

* …

*(please also add ideas, questions or examples in comments)*

Contributor guide

Open the contributing guide

Research direction

Start with Sentry's Settings - Integrations area and the existing PagerDuty integration behavior. Read the discussion in issue #99917 and the PagerDuty REST API requirements. Done means a Sentry REST API path can add a PagerDuty integration key to an existing integration without Sentry authenticating with PagerDuty.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
api, observability
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.