Dogfooding Request: GitLab Runbooks

Details

• Point of contact for this request: @awthomas
• If a call is needed, what is the proposed date and time of the call: n/a
• Additional call details (format, type of call): n/a

SRE Support Needed

The Jupyter-based interactive runbooks feature was introduced in GitLab 11.4 and is currently at the minimal maturity level. Internal stakeholders (including CEO and VPs) have asked whether infrastructure engineering teams can adopt the interactive runbooks feature where possible in order to help the Configure group identify and prioritize the right set of improvements needed to make this feature 'production ready' for external customers.

As a first step, we'd like to answer the following questions:

• Are there any areas where infrastructure engineers can incorporate the interactive runbooks feature into their current workflows? If so, when can we start using it?
• If not, can we conduct an analysis to determine if there are any missing features/requirements that we would need in place in order to adopt the interactive runbooks feature? E.g. usability or performance enhancements?