## Business goal Shift primary (Tier 1) incident response to the teams that own each service, following a DevOps ownership model, so the people closest to the code are the first responders for it. ## Impact Reduces time to resolution by routing incidents directly to the team with the most context, reduces reliance on a small central SRE team as the sole source of on-call coverage, and scales incident response capacity as GitLab's service footprint grows. ## Scope * Alert routing/rerouting so incidents reach the correct service-owning team by default * Fine-grained access to production systems, scoped so on-call engineers on service-owning teams can safely operate within their own service's boundaries * Enablement for onboarding teams into Tier 1 on-call (runbooks, training, on-call tooling, readiness criteria) ## DRI @thisisshreya ### Participants @sun_lee ## Exit criteria - [ ] Alert routing model defined and implemented for service-owning teams - [ ] Existing applicable alerts are routed to target teams - [ ] Fine-grained production access model implemented and available to on-call engineers on those teams - [ ] Onboarding/enablement process (runbooks, training, readiness checklist) defined for teams moving to Tier 1 - [ ] First cohort of teams receives their own alerts/pages first - [ ] AI - [ ] Fulfillment - [x] Runners Platform - [ ] Gitaly <!-- STATUS NOTE START --> ## Status 2026-08-19 :clock1: **total hours spent this week by all contributors**: 12 :status: We have made good progress in preparing materials for teams to onboard , merged documentation in [handbook](https://gitlab.com/gitlab-com/content-sites/handbook/-/merge_requests/20736),[onboarding checklist for STEOC](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/merge_requests/538),[Runbook](https://gitlab.com/gitlab-com/runbooks/-/merge_requests/11270) while [addressing questions / discussing access management for these teams to be successful in oncall](https://gitlab.com/gitlab-com/gl-infra/production-engineering/-/work_items/29364), once we have the basic onboarding materials ready , we can soon start onboarding our pilot teams :arrow_forward: **next**: - - Create an onboarding template for rotation leaders ( and us ) to plan and keep track of a phased migration to Tier-1 - Continue discussions around access management and figure out the best way to provide access to Tier-1 teams _Copied from https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/2067#note_3702692029_ <!-- STATUS NOTE END -->