The following page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features or functionality remain at the sole discretion of GitLab Inc.
Who's on call?
Getting the rotation streamlined can be the difference between a successful incident response or a prolonged outage and frustration for the responding team. Given that downtime is expensive, organizations need to treat on-call schedule management as the critical process that it actually is.
GitLab on-call schedule helps teams ensure the right person is always available, day or night, to quickly respond to incidents and outages.
On-call schedule is part of GitLab incident management to enable teams to effectively and efficiently respond and resolve incidents.
Our current Incident Management tools have been built for users who align with our Allison (Application Ops) and Ingrid (Infrastructure Operator) personas. The experience targets DevOps teams at smaller companies where it is common for the engineers to be on-call and responding to alerts for the software that they also write code for. As we mature this category, we will evolve the experience to appeal to and serve the enterprise customer. Here is a list of all jobs to be done (JTBD) for incident management.
On-call incident responders never miss an alert.
How are we tracking success?
Features in the On-Call category have been placed in tiers based on GitLab's Buyer Based Tiering strategy. The following pricing plan represents existing and future features.
|Email notifications for alerts||✅||✅||✅|