This video tells the story of a typical SRE journey with Rundeck. First, using Rundeck for creating standard operating procedures and checklists. Second, using Rundeck to safely enable Operations as a Service so others who are traditionally outside of the operations organization can execute operations procedures.
Standardizing procedures helps SREs save time, reduces errors (especially under pressure or when a procedure is critical but run infrequently), and makes it easier to spot anomalies (the outcome is different than expected, or log output is unexpected).
Self-service is great for an SRE for two reasons. First, by allowing others to execute operations procedures (like restarts, health checks, or standard maintenance), you are reducing the toil load on SREs (who can then dedicate more of their time to engineering work that eliminates that toil). Second, it helps keep operations out of the way of other teams. Rather than filling out tickets and waiting in queues, who wouldn't want a safe and secure "button" (GUI, CLI, or API) to take immediate action?
We hope you enjoyed this video. If you want to learn more about Rundeck, you might like this overview video.