Runbook Automation: How to Own and Develop your Service At the Same Time

Watch Now



Runbook Automation: How to Own and Develop Your Service At the Same Time

“You build it, you run it.”  Congratulations, you are responsible for creating, and also the care and feeding of your new critical business service.  Suddenly your developers are spending more time on tickets and less time on epics.  How can your devops teams continue to strive forward with innovation when they continue to get distracted with concerns of “now”?  

This is where runbooks and runbook automation can help.  Just as your build, test, and delivery are automated, so should your operations.  With runbook automation, now you can delegate automated tasks to other teams such as your operations team to assist with common and frequent tasks.  These can be lifecycle maintenance, such as backups and cache refreshes, and they can be triage and remediation tasks in the case of incidents.

Key Takeaways: 

  • How to organize for service ownership
  • Division of responsibilities with an ops team
  • What to automate in the life cycle of a service
  • How incident resolution works in service ownership
  • How to delegate self service operations using Rundeck
Mandi Walls

Mandi Walls is a DevOps Advocate at PagerDuty. For PagerDuty, she helps organizations along their IT Modernization journey. Prior to PagerDuty, she worked at Chef Software and AOL. She is an international speaker on DevOps topics and the author of the whitepaper “Building A DevOps Culture”, published by O’Reilly.