Skip to main content
Book a demo

Connect PagerDuty to GitHub Copilot

Give GitHub Copilot governed access to PagerDuty’s 18 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo GitHub Copilot setup guide

Set up

Add PagerDuty to GitHub Copilot in four steps

Admins approve the server once. Everyone in GitHub Copilot then gets it through the same governed connection.

  1. 1

    Approve PagerDuty in Runlayer

    Add PagerDuty from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches PagerDuty’s 18 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to PagerDuty

    Each user signs in to PagerDuty with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use PagerDuty from GitHub Copilot

    PagerDuty’s approved tools appear in GitHub Copilot. Every call is checked against policy and recorded.

Tools

18 PagerDuty tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Browse activity

    Read PagerDuty account activity (log entries).

  • Browse alert grouping

    Read PagerDuty alert grouping settings.

  • Browse change events

    Read PagerDuty change event data.

  • Browse escalation policies

    Read PagerDuty escalation policy data.

  • Browse event orchestrations

    Read PagerDuty event orchestration data.

  • Browse incidents

    Read PagerDuty incident data.

  • Browse schedules

    Read PagerDuty schedules and on-call data.

  • Browse services

    Read PagerDuty service data.

See all 18 PagerDuty tools

Control

What Runlayer can see and stop in GitHub Copilot

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot exposes to Runlayer.

  • Gateway policy (available)

    Every PagerDuty call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination