Built-in PagerDuty connector (and Opsgenie, incident.io)

Open
#52 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
python
Domain
api, backend

Research direction

Start by locating how existing connections and read tools are defined and how on-call-coverage accesses its data. Then identify the PagerDuty API and authentication requirements for the listed schedule, escalation policy, and incident reads. Validate against the stated schedule-gap scenario and confirm the report detects it.

Written by the indexing model from the issue text.

Description

area: connectors help wanted idea

Idea

Add on-call and incident data as a built-in connection, starting with PagerDuty.

Problem

on-call-coverage and incident-follow-up-review need schedules, escalation policies and incident timelines, which nothing built in provides today.

Proposed initial scope

  • A PagerDuty connection with a read-only API key or OAuth.
  • Read tools: list schedules and on-call users, get an escalation policy, list incidents, get an incident with its log entries.
  • Opsgenie and incident.io afterwards, with the same tool shapes where possible.

Validation

Run on-call-coverage against a PagerDuty account with a deliberate schedule gap, and confirm the report finds it.

Dominant language
Python
Stars
1
Forks
1
Avg merge
1h 9m
Merged PRs (30d)
322

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from piotrekno1/second-shift

All issues in piotrekno1/second-shift

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.