Runbooks are a collection of documented procedures that explain how to carry out a particular process, be it starting, stopping, debugging, or troubleshooting a particular system.
Historically, runbooks took the form of a decision tree or a detailed step-by-step guide depending on the condition or system.
Modern implementations have introduced the concept of an “executable runbooks”, where, along with a well-defined process, operators can execute pre-written code blocks or database queries against a given environment.
We aim to extend Incident Management further by rendering runbooks inside GitLab as interactive documents for operators; link from incident management screens so when an incident happens, we point you to the relevant runbook. Additionally, we want to allow runbooks to trigger ChatOps functions defined in gitlab-ci.yml.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
Now that users can easily access the contents of their repository to easily build runbooks, we want to refine some known issues in the integration in preparation of showing runbook content inside GitLab.
While there are some offerings in the marketplace, they rely on heavy customization for every use case and are somewhat specialized (ie networking).
VictorOps is an unified incident management platform that offers real-time alerting, collaboration, and documentation solutions for DevOps teams.
NetBrain technologies provides map-driven network automation solution.