Skip to main content
Book a demo

Connect PagerDuty to Crush

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

Book a demo Crush setup guide

Set up

Add PagerDuty to Crush in four steps

Admins approve the server once. Everyone in Crush 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 Crush to Runlayer

    Users add the Runlayer Plugin to Crush by following Runlayer’s setup guide. Crush reaches PagerDuty’s 18 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Crush 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 Crush

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

Tools

18 PagerDuty tools in Crush

Runlayer policy decides which of these Crush 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 Crush

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

  • Gateway policy (available)

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

  • Audit trail (available)

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

  • Native enforcement adapter (not available)

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

Frequently asked questions

Connect more

Find another combination