Orchestrator Best Practices BRAD WATTS DMVMUG Reston, VA
http://dmvmug.com Slide 2 Agenda Design and Planning Runbook
Planning Runbook Design Runbook Development Operations Runbook Best
Practices Monitoring and Operations Exporting/Importing Runbooks
Slide 3 Planning Slide 4 What to Automate What processes consume
the most time? What is affecting my service levels? Which problems
recur most frequently? Which of these are the most expensive for
the company? What failures are visible to the customer? Slide 5
Before Authoring Begins Is Orchestrator the right tool for the
task? Is it technically feasible? Cost and effort Time to recoup
investment Ports and Permissions Closing the loop with ITSM
integration Slide 6 Best candidates for runbook automation Recovery
Tasks Incident Remediation User Provisioning Slide 7 Return on
Investment Scenario 1 Automate manual task 1 time every month 20
minute task 1 week to build runbook 20 minutes X 12 months = 4
hours/year 40 hours / 4 hours = 10 years Slide 8 Return on
Investment Scenario 2 Service Stopped 1 alert per day Tier 1 (5
mins) Tier 2 (15 mins) 8 hours to build runbook 20 minutes X 365
days = 121 hours/year 8 hours / 20 minutes = 24 days Slide 9
Runbook Design Slide 10 General Rules Rename activities Re-Color
links Folder and runbook structure Naming convention Flow from left
to right No scrolling Modularize your runbooks Slide 11 Slide 12
Demo General Best Practices Slide 13 Fault Tolerance Infrastructure
level Runbook level Design to support failover Monitoring
activities Slide 14 Logging Do a process specific log a technical
log Dont use log files use SEND PLATFORM EVENT enable activity
specific logging Slide 15 Action Request
CollectValidateRecordExecute If you integrate your runbooks in
Service Manger, you get the first four for free! Slide 16 Operation
Slide 17 Runbook and Orchestrator monitoring Operations Manager
Management Pack Infrastructure and roles Services Events Custom
management pa Job history Queue Real time job dashboard Slide 18
Orchestrator Dashboard Slide 19 Demo Monitoring Slide 20 Runbooks
From DEV to Production Production Pre- production Sandbox Test
Sandbox Slide 21 Import/Export Process All development of runbooks
should occur in a Development Environment Export runbooks from
Development to Production Be careful about Global Variables Dont
make fixes in Production. Go back to Development! Slide 22 Demo
Exporting/Importing Runbooks Slide 23 Summary Dont Automate just to
Automate! Spend the time to plan before you jump in! Develop
standards for your Orchestrator Environment Always work in
Development! Slide 24 Questions Slide 25 Speakers Blog: Email:
[email protected] Need more information on DMVMUG Visit
www.dmvmug.com www.dmvmug.com Need more information on DMVMUG Visit
www.dmvmug.com www.dmvmug.com
