Failure is inevitable. But are you incurring more downtime and disruption than necessary? Legacy incident response techniques have difficulty keeping up with the increasing pace of change and skyrocketing complexity of today’s application environments.
During this webinar, you’ll learn about modern incident response techniques that can dramatically shorten incidents and reduce escalations. Join the experts from Rundeck and PagerDuty as they share:
*How a real-time operations platform intelligently manages alerts and on-call mobilization, delivering the right people the right information at the right time
*How runbook automation gives front-line response teams self-service access to run automated workflows – or runbooks – that diagnose and resolve incidents without escalating to an expert.
*How to automatically detect, diagnose, and resolve incidents without human intervention.
8. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
9. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
10. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
11. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
12. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
13. Proprietary & Confidential
PagerDuty - The Basics
+ Proactively manage your real
time operations
+ Harness digital data
+ Make sense of data
+ Respond & engage teams
+ Analyze & learn
15. Proprietary & Confidential
Rundeck - The Basics
is runbook automation.
Give anyone in your organization self-service access to
operations tasks that previously only your subject matter
experts could perform.
16. Proprietary & Confidential
Rundeck - The Basics
Dev SRE NOC Security Support
Define Automated
Workflows Across:
SME
● Tools
● Scripts
● APIs
● Manual Commands
Cloud, Physical, VMs,
Containers, Serverless
Anyone
Anything
Anywhere
Enable
to do
it’s needed
22. Proprietary & Confidential
Rundeck + PagerDuty Rewrites the Incident Timeline
Detect
30 min
Mobilize
1 hr
Resolve
2 hr
Learn
2 days
Incident Volume
Before
Diagnose
1 hr
Detect &
Prevent
5 min
Mobilize
< 1 min
Resolve
30 min
Learn
2 days
With PagerDuty
Incident Volume
Diagnose
30 min
Resolve
15 min
Learn
1 day
PagerDuty and
Rundeck Together
Incident Volume
23. Proprietary & Confidential
Accelerate Incident Resolution with Automation
PagerDuty and Rundeck
are used together to
prevent and reduce the
duration of incidents
by incorporating
automation seamlessly
into the incident
response process.
Attempting
auto-remediation before
engaging responder
Provide common
diagnostic and
remediation tasks to
responders during the
incident
Audit trail of automated
tasks for more effective
post-mortem analysis
24. Proprietary & Confidential
Benefits of Using Rundeck with PagerDuty
Use PagerDuty to alert the
right individual or team,
while using automation to
assist them in diagnosis
and remediation.
Prevent Incidents and
Reduce Incident Duration
Stop relying on large teams
of individuals performing
manual actions. Empower
individuals and small groups
to take the actions necessary
to resolve issues.
Reduce the Cost
of Response
Reduce reliance on your
heroes’ tribal knowledge,
leading to burnout. Keep current
operational procedures in a
system that is accessible
by multiple stakeholders.
Share Knowledge and
Continuously Improve
25. Proprietary & Confidential
Integration Overview
Automatically trigger Rundeck jobs at start of
PagerDuty incident.
Trigger Rundeck jobs during an incident using
PagerDuty custom actions.
Have your Rundeck jobs update incident notes in
PagerDuty.
Rundeck notifications can trigger a PagerDuty incident.