# Invoking Scripts to Enrich Incidents
# Solution Summary
There are many cases where enriching incidents with "diagnostic data" can be accomplished with existing scripts, but those scripts must be invoked from within your secure environment. PagerDuty's Automation Actions (opens new window) provides a fast and simple method for invoking commands and scripts from 'behind the firewall' right from within the PagerDuty user-interface.
This solution provides instructions for setting up Automation Actions to retrieve and invoke a script from Github in order to reduce investigation and troubleshooting time.
Watch a demo of Automation Actions here:
# Create Automation Actions Runner
In order to install the Automation Actions runner, you must have a server available where you can install Java 11+. Linux is the recommended operating system, though you can optionally run the Automation-Actions Jar in a container.
# Download Runner Credentials File
- Create a PagerDuty API Key
- In the PagerDuty web app, navigate to Integrations -> API Access Keys and click Create New API Key.
- Enter a Description that will help you identify the key later on. If you would like it to be read-only, check the Read-only option.
- Click Create Key
- A unique API key will be generated. Copy it to a safe place, as you will not have access to copy this key again. Once it has been copied, click Close.
- If you lose a key you will need to delete it and create a new one.
- In PagerDuty, navigate to Automation -> Rundeck Actions -> Runners tab -> +Add Runner
- Enter a Name and Description and click Next, then Generate Runner Secret & ID.
- On the following screen, click Download ID & Secret to download the file
credentials.pdrunner-creds, and click Confirm.
credentials.pdrunner-credsin your preferred text editor, replace
<API_Token>with the PagerDuty API key from step 1 above, and save the file:
id:XXXXXXXXXXXXXXXXXXXXXXX3P1C secret:XXXXXXXXXXXXXXXXXXXX2I4B token:<PagerDuty_API_TOKEN> rundeck_url: http://localhost:4440 rundeck_token: <Your_Saved_RUNDECK_API_TOKEN>
# Deploy Runner
- [Optional] Update the machine where you will install the runner
sudo apt-get update(Debian) or
sudo yum update(RHEL/CentOS).
- If you have not installed Java 11+ yet, install it with
sudo apt install openjdk-11-jre-headless.
mkdir rundeck_runner: Create a folder in a preferred directory on your system to place the credentials files.
cd rundeck_runner: Navigate into the runner’s directory.
- Copy the credentials file that was downloaded from the PagerDuty Runner menu in the last section. It should already contain the PagerDuty API key inside the file.
mv credentials.pdrunner-creds .pdrunner-creds: This will rename the file to
.pdrunner-creds. Make sure that this file is in the
wget https://runbook-actions.pagerduty.com/pd-runner.jar: Download the latest runner software from PagerDuty.
java -jar pd-runner.jar &: Launch pd-runner in detached mode.
- [Optional] Verify activity in runner.log:
tail -f /home/ubuntu/rundeck_runner/runner/logs/runner.log
- Check the runner’s status in PagerDuty. A green checkmark indicates that the runner is active and running successfully. A red circle indicates that the runner is not running or there is a problem with the runner:
# Create Diagnostic Data Automation Action
Once the runner is running successfully, you can add an action.
- In PagerDuty, select the Actions tab and click Add Action
- Enter the desired values for the Name and Describe the Action fields.
- Use the Script type for the Select Type dropdown.
- Use the Diagnostic options for the Type of Action dropdown:
- In the Define Your Action field, you have the option to edit and execute a raw script here, or use commands to pull a script (e.g. from Github), then invoke and delete it from the Runner.
These scripts are sample code to demonstrate the different ways you can implement Automation Actions. They are not meant for use within your production environment.
- In the Identify where this action will be run section, select the Runner that you configured in the previous section and then select the Services that you want this Action to be associated with.
- In the Associate with team(s) section, select the team or teams that will have access to run this action.
- Click Update Action.
# Invoke Diagnostic Data Action
Now that the Runner has been deployed and the Automation Action has been configured, when incidents are created on the Services associated with the Automation Action, there will be an option in the Run Actions dropdown that will trigger the automation:
This will produce records on the Incident Timeline showing that this Action was invoked. Click on output report:
This will take you to the output report page where you can view the log-output of the Automation Action: