Gitlab hero border pattern left svg Gitlab hero border pattern right svg

Reliability Engineering

Workflow How may we be of service? Status STATUS
Issue Trackers Infrastructure: Milestones, OnCall Production: Incidents, Changes, Deltas Delivery
Slack Channels #sre-lounge, #database #alerts, #production #g_delivery
Operations Runbooks (please contribute!) On-call: Handover Document, Reports  


Reliability Engineering teams are the gatekeepers and primary caretakers of the operational environment hosting all of GitLab's user-facing services (most notably, focusing on their availability, performance and scalability through reliability considerations.


Reliability Engineering team are composed of DBREs and SREs. As the role titles indicate, they have different areas of specialty but focus on the reliability of the environment as the unifying goal.

Reliability Engineering teams own the following operational processes:

The teams' overarching goal with respect to these processes is to outdate them through automation.

Key Metrics

Key metrics related to this group include:


Each member of the Site Reliability Team is part of this vision:

Team Members

The following people are members of the Reliability Engineering Teams:

Reliability Engineering, Secure & Defend

Person Role

Reliability Engineering, CI/CD & Enablement

Person Role

Reliability Engineering, Dev & Ops

Person Role