PagerDuty Automation Trial
PagerDuty’s Automation Trial provides incident responders with two key feature sets, Automation Actions and Runbook Automation.
Runbook Automation is PagerDuty’s fully managed SaaS automation platform providing online secure access to the latest commercial Rundeck feature set. Runbook Automation can be connected to Automation Actions, which allow users to run automation jobs defined in their Rundeck service within PagerDuty. With Runbook Automation, platform engineering and SRE teams are able to standardize and automate cloud ops, and in the context of incident response, Runbook Automation will help reduce incident time and the total number of escalations.
Runbook Automation connects your IT infrastructure through a Runner that is deployed within a firewall or virtual private cloud and provides an encrypted connection back the Runbook Automation endpoint. The Runbook Runner is built to meet the latest zero-trust security models. It calls back to the Runbook Automation endpoint via HTTPS (port 443). There’s no need to open additional ports in firewalls.
Automation Actions is a first-class integration between PagerDuty's incident response capabilities and cloud automation platform. Automation Actions are available directly within the PagerDuty UI so that your incident responders can enrich the incident timeline with the results of diagnostics created in your Runbook Automation trial account. Invoke Automation Actions while working from anywhere via Slack, Microsoft Teams, or the PagerDuty mobile app. Delegate automation tasks to first responders and customer service agents to shorten resolution times and fewer disruptive escalations.
Availability
The 14-day trial is available to existing customers on the following pricing plans: Business, Digital Operations (legacy) and Enterprise for Incident Management. If you'd like to upgrade to a pricing plan that features this trial, please contact our Sales team.
Required User Permissions
The Account Owner can activate the trial. All other user roles can request a trial, which will send an email notification to the Account Owner to activate the trial.
Activate the Trial
The Account Owner can activate the Automation trial in two places: on a resolved incident, or on the Automation Actions page.
- Navigate to any resolved incident in your PagerDuty account, or navigate to Automation Automation Actions.
- From the Run Actions dropdown, select Activate trial.
- Select the admin for your Runbook Automation account by entering their email address.
- Select a subdomain name for your Runbook Automation instance.
- Click Begin Trial.
After activating the Automation trial, you will have immediate access to Automation Actions, though Runbook Automation may take a few moments to initialize.
Request the Trial
All users other than the Account Owner can request the Automation trial in two places: on a resolved incident or on the Automation Actions page.
- Navigate to any resolved incident within your PagerDuty account, or navigate to Automation Automation Actions.
- Select the Run Actions button and select Activate trial.
- An email notification will be sent to the Account Owner requesting they activate the Automation trial.
- You will receive a welcome email once the Account Owner activates the trial.
Extend Your Trial or Make a Purchase
If you wish to extend the Automation trial or if you wish to purchase Automation products, please contact our Sales team.
End Your Trial
If you wish to end the Automation trial early, please reach out to our Sales team.
What to Expect During the Trial
Your activation email will contain the resources you need to get started with the Automation trial. You can read Automation Actions for more information about automating repeatable actions in PagerDuty, or read Automated Diagnostics to learn more about the included, pre-built diagnostics jobs.
A quick, self-guided tour on the Automation Actions page will also walk you through how to create an action.
FAQ
How long does the trial last?
The trial lasts 14 days. The trial will not end on a weekend and will wait for the next business day to terminate.
What happens if I do not convert to a paid version of Automation at the end of the trial?
If you do not convert to a paid version by the end of the trial, your PagerDuty account will lose all Automation features. Any event rules you have configured will remain, but references to Automation will be removed. The Automation Actions Runners and Actions will be deleted and will no longer display on incidents' detail pages. The Runbook Automation login information will be disabled for all users. Any configurations you have made will be removed and not retained.
Where is Runbook Automation hosted?
Runbook Automation is hosted in several AWS US regions.
What does the error ConfigurationFailure: Local Executor is disabled error mean?
ConfigurationFailure: Local Executor is disabled error mean?This error indicates that the local command execution in Runbook Automation that connects to the instance via a shell is disabled for security reasons. Make sure that command execution is running on the Remote Runners, or dispatched to a node through the Remote Runners.
What, if any, IP addresses do I need to safelist, and what ports do I need open?
Runbook Automation web URL IP addresses are unlikely to change, but may do so in the future. All DNS records resolve to multiple IPs, which you can find by querying the A records for your subdomain using dig or nslookup. When using the Runner feature, your system must be able to make outbound HTTPS connections to your subdomain on TCP port 443.
Updated about 2 months ago