Downtime happens, but GitLab Incident Management can help
Nov 30, 2021Itzik Gan Baruch

Summary
This post introduces GitLab Incident Management as a built-in feature of the DevOps Platform. It details the costs of downtime, defines incidents and incident management, and explains the benefits of managing incidents within GitLab due to the co-location of code, CI/CD, and monitoring tools. It outlines the process of creating incidents manually or automatically via webhooks (e.g., PagerDuty), managing alerts, setting up on-call schedules, defining escalation policies, and the current notification methods (email, with plans for Slack, SMS, and phone calls).
More from the High Availability trail
- Consolidate your GitLab stack with Gitaly on Kubernetes
- GitLab backs 99.9% availability SLA with service credits
- How we are closing the gap on replicating *everything* in GitLab Geo
- How we tested a feature that affected (almost) all parts of GitLab
- Meet Praefect: The traffic manager making your Git data highly available