Skip to main content

Automated Diagnostics

Automated Diagnostics

Integrating with Automation Actions

The prebuilt Jobs in the Automated Diagnostics solution are designed to be invoked from Automation Actionsopen in new window, though they can be invoked from within the Runbook Automation or Process Automation interface as well.

Heads Up

The steps for configuration differ for Runbook Automation and Process Automation (self-hosted). Be sure to select the correct tab below for the applicable instructions.

Create a Runbook Automation API Key

  1. Click on the User Icon in the upper-right and click on Profile.
  2. To the right of User API Tokens, click +: RD Token

  3. Enter a name for the API token and click Generate New Token.
  4. Copy the User API Token and keep it in a safe place for later use.

Create an Action Runner

Next, you will add a new runner in PagerDuty to connect to Runbook Automation.

  1. In PagerDuty, navigate to Automation -> Automation Actions -> Runners tab -> +Add Runner
  2. Select Runbook Automation as the type of Runner and click Next

  3. Enter a Name and Description and click Next

  4. On the following screen, enter your Runbook Automation Subdomain and the API key you saved previously. Optionally, associate with specific teams to limit who can use this Runner.

  5. Click Create Runner
  6. Check the runner’s status in PagerDuty

    A green checkmark indicates that the connection to your Runbook Automation instance was configured correctly.
    A red circle indicates that the connection was unsuccessful. In this case, make sure you typed the subdomain and API Token correctly.

Define an Action

  1. In PagerDuty, navigate to Automation -> Rundeck Actions -> Add Action:

  2. Select your Runner and click Next

  3. Select the Third Party Service Disruptions job from those listed and click Next

  4. Review and update the Action Name and Description if desired.
  5. Select one or more Services. This controls which incidents will have this action.
  6. If desired, select one or more Teams. This limits access for this action to members of those teams. Leave blank to make universally available in the selected services.

  7. Click Next
  8. Insert -pd_incident_id ${pagerduty.incidentId} into the Enter arguments field.

  9. Click Create Action. This Automated Action can now be invoked from an incident or from Event Orchestrationopen in new window:
Invoke from Incident
Invoke from Incident

Heads Up

Although the Action can be invoked from PagerDuty, the output of the Job will not yet appear on the Incident Timeline. Continue on to the next sectionopen in new window to complete the setup