# Production Change ## Change Summary Enable the Topology Service client for GitLab.com (cell-1) in production. This allows the Rails application to communicate with the Topology Service via mTLS certificates for cell routing functionality. ### Change impact As a consequence of this change, the GitLab Rails application running on gitlab.com infrastructure will be treated as one isolated `legacy cell` (cell-1). All authenticated and unauthenticated requests will have a `cell-1` prefix added to the `_gitlab_session` cookie. HTTP Router will start classifying the requests against Topology Service. HTTP Router will initiate classification by sending a payload of the `_gitlab_session` cookie to the Topology Service (Runway) `/v1/classify` endpoint and receive a classification response. Most of the requests will be cached on the HTTP Router worker side, which will reduce the load on Topology Service. By enabling this configuration, Topology Service will be part of the critical path for gitlab.com request flow. **Risk: High** — The Topology Service client is on the critical path for user request flow, as it leverages the `/v1/classify` route for all web requests. ### Epic This Change Request is part of: https://gitlab.com/gitlab-com/gl-infra/tenant-scale/cells-infrastructure/team/-/work_items/553 ### Escalation path HTTP Router and Topology service are managed and maintained by ~"group::cells infrastructure" and ~"group::tenant services", in case of emergency contact the following slack channels: * `#g_tenant_services` Engineering manager: @jarv * `#g_cells_infrastructure` Engineering manager @daveyleach ### Failure story Previous attempt to enable this configuration led to production [incident](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21146) FCL Epic: https://gitlab.com/gitlab-com/feature-change-locks/-/work_items/77 All FCL follow ups have been resolved. ### Prerequisites Here is the list of all prerequisites has been made to make sure this configuration change is smooth and transparent. * Topology service has been configured to enable legacy cell configuration: https://ops.gitlab.net/gitlab-com/gl-infra/cells/topology-service-deployer/-/merge_requests/144 * Topology service health check has been deployed and tested on [`gprd-cny`](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5253) * Topology service health check has been deployed and tested on [`gprd`](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5254) * Topology service health check test results: https://gitlab.com/gitlab-com/gl-infra/tenant-scale/cells-infrastructure/team/-/work_items/553#note_3153981376 **Testing**: * Successfully tested in staging: https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5064 * Topology service health check has been tested on all environments, including `gprd`: https://gitlab.com/gitlab-com/gl-infra/tenant-scale/cells-infrastructure/team/-/work_items/553#note_3153981376 ## Change Details <!-- To automatically add your change to the GitLab Production calendar update the following fields: - Time tracking - Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM) Bot: https://gitlab.com/gitlab-com/gl-infra/ops-team/toolkit/change-scheduler --> 1. **Services Impacted** - GitLab Rails (web, api, git, websockets, sidekiq) 1. **Change Technician** - @vglafirov 1. **Change Reviewer** - @tkhandelwal3 @gitlab-org/saas-platforms/change-review-leadership 1. **Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM)** - 2026-03-20 08:00 1. **Time tracking** - 180 min 1. **Downtime Component** - None > [!IMPORTANT] > If your change involves scheduled maintenance, add a step to set and > [unset maintenance mode](https://gitlab.com/gitlab-com/runbooks/-/blob/master/docs/monitoring/set_maintenance_window.md) > per our runbooks. This will make sure SLA calculations adjust for the maintenance period. ## Preparation > [!NOTE] > The following checklists must be done in advance, before setting the label ~"change::scheduled" ### Change Reviewer checklist <!-- To be filled out by the reviewer. --> ~C4 ~C3 ~C2 ~C1: - [x] Check if the following applies: - The **scheduled day and time** of execution of the change is appropriate. - The [change plan](#detailed-steps-for-the-change) is technically accurate. - The change plan includes **estimated timing values** based on previous testing. - The change plan includes a viable [rollback plan](#rollback). - The specified [metrics/monitoring dashboards](#key-metrics-to-observe) provide sufficient visibility for the change. ~C2 ~C1: - [x] Check if the following applies: - The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details). - The change plan includes success measures for all steps/milestones during the execution. - The change adequately minimizes risk within the environment/service. - The performance implications of executing the change are well-understood and documented. - The specified metrics/monitoring dashboards provide sufficient visibility for the change. - If not, is it possible (or necessary) to make changes to observability platforms for added visibility? - The change has a primary and secondary SRE with knowledge of the details available during the change window. - The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval. - The labels ~"blocks deployments" and/or ~"blocks feature-flags" are applied as necessary. ### Change Technician checklist - [x] The [Change Criticality](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#change-criticalities) has been set appropriately and requirements have been reviewed. - [x] The [change plan](#detailed-steps-for-the-change) is technically accurate. - [x] The [rollback plan](#rollback) is technically accurate and detailed enough to be executed by anyone with access. - [x] This Change Issue is linked to the appropriate Issue and/or Epic - [x] Change has been tested in staging and results noted in a comment on this issue. - [x] A dry-run has been conducted and results noted in a comment on this issue. - [x] The change execution window respects the [Production Change Lock periods](https://about.gitlab.com/handbook/engineering/infrastructure/change-management/#production-change-lock-pcl). - [x] Once all boxes above are checked, mark the change request as scheduled: `/label ~"change::scheduled"` - [x] For ~C1 and ~C2 change issues, the change event is added to the [GitLab Production](https://calendar.google.com/calendar/embed?src=gitlab.com_si2ach70eb1j65cnu040m3alq0%40group.calendar.google.com) calendar by the [change-scheduler bot](https://gitlab.com/gitlab-com/gl-infra/ops-team/toolkit/change-scheduler). It is schedule to run every 2 hours. - [x] For ~C1 and ~C2 change issues, Platform Leadership provides approval with the ~platform_leadership_approved label on the issue. Mention `@gitlab-org/saas-platforms/change-review-leadership` in this issue with a reference to [review guidelines](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/platform-leadership-review/) to get approval and provide visibility to all infrastructure managers. - [x] For ~C1, ~C2, or ~"blocks deployments" change issues, confirm with Release managers that the change does not overlap or hinder any release process (In `#production` channel, mention `@release-managers` and this issue and await their acknowledgment.) - [x] For ~C1 change issues or ~C2 change issues happening during weekend, SREs on-call must be informed [at least 2 weeks in advance](https://handbook.gitlab.com/handbook/engineering/infrastructure-platforms/change-management/#approval). Check [the incident.io GitLab.com Production EOC schedule](https://app.incident.io/gitlab/on-call/schedules/01K5YWAGZ7YCQGAG7ATQ9XQWHW) to find who will be on-call at the scheduled day and time. ## Detailed steps for the change ### Pre-execution steps > [!NOTE] > The following steps should be done right at the scheduled time of the change request. The [preparation steps](#preparation) are > listed below. - [x] Make sure all tasks in [Change Technician checklist](#change-technician-checklist) are done - [x] For ~C1 and ~C2 change issues, the SRE on-call has been informed prior to change being rolled out. - [x] The SRE on-call provided approval with the ~eoc_approved label on the issue. - [ ] For ~C1, ~C2, or ~"blocks deployments" change issues, Release managers have been informed prior to change being rolled out. (In `#production` channel, mention `@release-managers` and this issue and await their acknowledgment.) - [x] There are currently no [active incidents](https://gitlab.com/gitlab-com/gl-infra/production/-/issues/?sort=created_date&state=opened&label_name%5B%5D=Incident%3A%3AActive&or%5Blabel_name%5D%5B%5D=severity%3A%3A1&or%5Blabel_name%5D%5B%5D=severity%3A%3A2&first_page_size=20) that are ~severity::1 or ~severity::2 - [x] If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change. ### Change steps - steps to take to execute the change ### Expected log entries ```sh [TopologyService] INFO: Cell '1' validated (address: gitlab.com) [TopologyService] INFO: Cell validation passed ``` *Estimated Time to Complete (mins)* - 180 minutes - [x] Set label ~"change::in-progress" `/label ~change::in-progress` #### GPRD-CNY environment - [x] Merge `gprd-cny` [MR](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5270) - [x] Monitor deployment pipeline for any failures and wait for pipeline to finish - [x] Connect to `gprd` k8s cluster - [x] Execute `glsh kube use-cluster gprd` - [x] Watch webservices pods which are not in `Running` state in `gitlab-cny` namespace. - [x] `watch kubectl get pods -n gitlab-cny -l "app=webservice" --field-selector="status.phase!=Running"` - [x] Make sure pods are not crashing - [x] Get pods logs for some randomly picked newly created `gitlab-cny-webservice-*` pods - [x] Check if topology service Health Check has the [expected logs](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#expected-log-entries). - [x] [Monitor and observe](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#monitoring) - [x] Wait for 45 minutes #### GPRD regional `gprd-us-east1-b` - [x] Merge `gprd-us-east1-b` [MR](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5283) - [x] Monitor deployment pipeline for any failures and wait for pipeline to finish - [x] Connect to `gprd-us-east1-b` regional cluster - [x] Execute `glsh kube use-cluster gprd-us-east1-b` - [x] Watch webservices pods which are not in `Running` state in `gitlab` namespace. - [x] `watch kubectl get pods -n gitlab -l "app=webservice" --field-selector="status.phase!=Running"` - [x] Make sure pods are not crashing - [x] Get pods logs for some randomly picked newly created `gitlab-webservice-*` pods - [x] Check if topology service Health Check has the [expected logs](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#expected-log-entries). - [x] [Monitor and observe](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#monitoring) - [x] Wait for 45 minutes #### GPRD `gprd`, `gprd-us-east1-c` and `gprd-us-east1-d` clusters - [x] Merge `gprd` [MR](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5271) - [x] Monitor deployment pipeline for any failures and wait for pipeline to finish - [x] Connect to `gprd` k8s cluster - [x] Execute `glsh kube use-cluster gprd` - [x] Watch sidekiq pods which are not in `Running` state in `gitlab` namespace. - [x] `watch kubectl get pods -n gitlab -l "app=sidekiq" --field-selector="status.phase!=Running"` - [x] Make sure pods are not crashing - [x] Get pods logs for some newly created `gitlab-sidekiq-*` pods - [x] Check if topology service Health Check has the [expected logs](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#expected-log-entries) #### GPRD regional `gprd-us-east1-c` - [x] Connect to `gprd-us-east1-c` regional cluster - [x] Execute `glsh kube use-cluster gprd-us-east1-c` - [x] Watch webservices pods which are not in `Running` state in `gitlab` namespace. - [x] `watch kubectl get pods -n gitlab -l "app=webservice" --field-selector="status.phase!=Running"` - [x] Make sure pods are not crashing - [x] Get pods logs for some randomly picked newly created `gitlab-webservice-*` pods - [x] Check if topology service Health Check is working properly. #### GPRD regional `gprd-us-east1-d` - [x] Connect to `gprd-us-east1-d` regional cluster - [x] Execute `glsh kube use-cluster gprd-us-east1-d` - [x] Watch webservices pods which are not in `Running` state in `gitlab` namespace. - [x] `watch kubectl get pods -n gitlab -l "app=webservice" --field-selector="status.phase!=Running"` - [x] Make sure pods are not crashing - [x] Get pods logs for some randomly picked newly created `gitlab-webservice-*` pods - [x] Check if topology service Health Check is working properly. - [x] [Monitor and observe](https://gitlab.com/gitlab-com/gl-infra/production/-/work_items/21546#monitoring) - [x] Wait for 45 minutes - [x] Set label ~"change::complete" `/label ~change::complete` ## Rollback ### Rollback steps - steps to be taken in the event of a need to rollback this change *Estimated Time to Complete (mins)* - 30 minutes - [ ] In case issues found during rolling out to `gprd-cny` environment, the fastest way to mitigate it is to drain the canary (stop all production traffic to canary stage) - [ ] run in `#production` Slack channel: `/chatops gitlab run canary --disable --gprd` - [ ] In case issues is widespread and affecting most of production traffic, as immediate mitigation, we should disable Cloudflare routing rule for `gitlab.com/*` and exclude HTTP Router from the requests flow. - [ ] Remove `gitlab.com/*` routing rule from [CloudFlare configuration](https://dash.cloudflare.com/852e9d53d0f8adbd9205389356f2303d/workers/services/view/production-gitlab-com-cells-http-router/production/settings) - [ ] **Note**: If routing rule removed from CloudFlare manually, it will be reenabled on the next Terraform run per this [code](https://ops.gitlab.net/gitlab-com/gl-infra/config-mgmt/-/blob/cef7158f9e92fae0e8aaa93f7ea78f74f9440dc5/environments/gprd/cloudflare-workers.tf#L9). Create MR to disable this, in case we need to remove this rule permanently. - [ ] Rollback `gprd` [MR](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5271) - [ ] Rollback `gprd-cny` [MR](https://gitlab.com/gitlab-com/gl-infra/k8s-workloads/gitlab-com/-/merge_requests/5270) - [ ] Set label ~"change::aborted" `/label ~change::aborted` ## Monitoring ### Key metrics to observe <!-- * Describe which dashboards and which specific metrics we should be monitoring related to this change using the format below. --> - Metric: topology-rest Service RPS - Location: [topology-rest Service RPS](https://dashboards.gitlab.net/d/topology-rest-main/topology-rest3a-overview?from=now-1h&orgId=1&timezone=utc&to=now&var-PROMETHEUS_DS=mimir-runway&var-environment=gprd&viewPanel=panel-1625573293) - What changes to this metric should prompt a rollback: Increase in RPS is expected, significant drop in RPS indicates the failure - Metric: topology-rest Service Error Ratio - Location: [topology-rest Service Error Ratio](https://dashboards.gitlab.net/d/topology-rest-main/topology-rest3a-overview?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-runway&var-environment=gprd&viewPanel=panel-1971427134) - What changes to this metric should prompt a rollback: Increase in error ratio - Logs: Topology service error logs - Location: [Topology service error logs](https://dashboards.gitlab.net/explore?schemaVersion=1&panes=%7B%22iiu%22%3A%7B%22datasource%22%3A%22clickhouse-runway-production%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22datasource%22%3A%7B%22type%22%3A%22gitlab-clickhouse-datasource%22%2C%22uid%22%3A%22clickhouse-runway-production%22%7D%2C%22pluginVersion%22%3A%224.10.2%22%2C%22editorType%22%3A%22builder%22%2C%22rawSql%22%3A%22SELECT+TimestampTime+as+%5C%22timestamp%5C%22%2C+Body+as+%5C%22body%5C%22%2C+SeverityText+as+%5C%22level%5C%22%2C+Attributes+as+%5C%22labels%5C%22+FROM+%5C%22observability%5C%22.%5C%22otel_logs%5C%22+WHERE+%28+timestamp+%3E%3D+%24__fromTime+AND+timestamp+%3C%3D+%24__toTime+%29+AND+%28+level+%21%3D+%27info%27+%29+AND+%28+ServiceName+%3D+%27topology-rest%27+%29+AND+%28+labels%5B%27uri%27%5D+%3D+%27%2Fv1%2Fclassify%27+%29+ORDER+BY+timestamp+DESC+LIMIT+1000%22%2C%22builderOptions%22%3A%7B%22database%22%3A%22observability%22%2C%22table%22%3A%22otel_logs%22%2C%22queryType%22%3A%22logs%22%2C%22mode%22%3A%22list%22%2C%22columns%22%3A%5B%7B%22name%22%3A%22TimestampTime%22%2C%22hint%22%3A%22time%22%7D%2C%7B%22name%22%3A%22SeverityText%22%2C%22hint%22%3A%22log_level%22%7D%2C%7B%22name%22%3A%22Body%22%2C%22hint%22%3A%22log_message%22%7D%2C%7B%22name%22%3A%22Attributes%22%2C%22hint%22%3A%22log_labels%22%7D%5D%2C%22meta%22%3A%7B%22otelVersion%22%3A%22latest%22%2C%22otelEnabled%22%3Afalse%2C%22logMessageLike%22%3A%22%22%7D%2C%22limit%22%3A1000%2C%22filters%22%3A%5B%7B%22type%22%3A%22datetime%22%2C%22operator%22%3A%22WITH+IN+DASHBOARD+TIME+RANGE%22%2C%22filterType%22%3A%22custom%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22time%22%2C%22condition%22%3A%22AND%22%7D%2C%7B%22type%22%3A%22string%22%2C%22operator%22%3A%22%21%3D%22%2C%22filterType%22%3A%22custom%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22log_level%22%2C%22condition%22%3A%22AND%22%2C%22value%22%3A%22info%22%7D%2C%7B%22filterType%22%3A%22custom%22%2C%22key%22%3A%22ServiceName%22%2C%22type%22%3A%22LowCardinality%28String%29%22%2C%22condition%22%3A%22AND%22%2C%22operator%22%3A%22%3D%22%2C%22label%22%3A%22ServiceName%22%2C%22value%22%3A%22topology-rest%22%7D%2C%7B%22condition%22%3A%22AND%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22log_labels%22%2C%22mapKey%22%3A%22uri%22%2C%22type%22%3A%22Map%28String%2C+String%29%22%2C%22filterType%22%3A%22custom%22%2C%22operator%22%3A%22%3D%22%2C%22value%22%3A%22%2Fv1%2Fclassify%22%7D%5D%2C%22orderBy%22%3A%5B%7B%22name%22%3A%22%22%2C%22hint%22%3A%22time%22%2C%22dir%22%3A%22DESC%22%2C%22default%22%3Atrue%7D%5D%7D%2C%22format%22%3A2%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-1h%22%2C%22to%22%3A%22now%22%7D%2C%22panelsState%22%3A%7B%22logs%22%3A%7B%22sortOrder%22%3A%22Descending%22%7D%7D%2C%22compact%22%3Afalse%7D%7D&orgId=1) - What changes to this metric should prompt a rollback: Errors in logs - Logs: Topology service logs - Location: [Topology service logs](https://dashboards.gitlab.net/explore?schemaVersion=1&panes=%7B%22iiu%22%3A%7B%22datasource%22%3A%22clickhouse-runway-production%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22datasource%22%3A%7B%22type%22%3A%22gitlab-clickhouse-datasource%22%2C%22uid%22%3A%22clickhouse-runway-production%22%7D%2C%22pluginVersion%22%3A%224.10.2%22%2C%22editorType%22%3A%22builder%22%2C%22rawSql%22%3A%22SELECT+TimestampTime+as+%5C%22timestamp%5C%22%2C+Body+as+%5C%22body%5C%22%2C+SeverityText+as+%5C%22level%5C%22%2C+Attributes+as+%5C%22labels%5C%22+FROM+%5C%22observability%5C%22.%5C%22otel_logs%5C%22+WHERE+%28+timestamp+%3E%3D+%24__fromTime+AND+timestamp+%3C%3D+%24__toTime+%29+AND+%28+ServiceName+%3D+%27topology-rest%27+%29+AND+%28+labels%5B%27uri%27%5D+%3D+%27%2Fv1%2Fclassify%27+%29+ORDER+BY+timestamp+DESC+LIMIT+1000%22%2C%22builderOptions%22%3A%7B%22database%22%3A%22observability%22%2C%22table%22%3A%22otel_logs%22%2C%22queryType%22%3A%22logs%22%2C%22mode%22%3A%22list%22%2C%22columns%22%3A%5B%7B%22name%22%3A%22TimestampTime%22%2C%22hint%22%3A%22time%22%7D%2C%7B%22name%22%3A%22SeverityText%22%2C%22hint%22%3A%22log_level%22%7D%2C%7B%22name%22%3A%22Body%22%2C%22hint%22%3A%22log_message%22%7D%2C%7B%22name%22%3A%22Attributes%22%2C%22hint%22%3A%22log_labels%22%7D%5D%2C%22meta%22%3A%7B%22otelVersion%22%3A%22latest%22%2C%22otelEnabled%22%3Afalse%2C%22logMessageLike%22%3A%22%22%7D%2C%22limit%22%3A1000%2C%22filters%22%3A%5B%7B%22type%22%3A%22datetime%22%2C%22operator%22%3A%22WITH+IN+DASHBOARD+TIME+RANGE%22%2C%22filterType%22%3A%22custom%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22time%22%2C%22condition%22%3A%22AND%22%7D%2C%7B%22type%22%3A%22string%22%2C%22operator%22%3A%22IS+ANYTHING%22%2C%22filterType%22%3A%22custom%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22log_level%22%2C%22condition%22%3A%22AND%22%7D%2C%7B%22filterType%22%3A%22custom%22%2C%22key%22%3A%22ServiceName%22%2C%22type%22%3A%22LowCardinality%28String%29%22%2C%22condition%22%3A%22AND%22%2C%22operator%22%3A%22%3D%22%2C%22label%22%3A%22ServiceName%22%2C%22value%22%3A%22topology-rest%22%7D%2C%7B%22condition%22%3A%22AND%22%2C%22key%22%3A%22%22%2C%22hint%22%3A%22log_labels%22%2C%22mapKey%22%3A%22uri%22%2C%22type%22%3A%22Map%28String%2C+String%29%22%2C%22filterType%22%3A%22custom%22%2C%22operator%22%3A%22%3D%22%2C%22value%22%3A%22%2Fv1%2Fclassify%22%7D%5D%2C%22orderBy%22%3A%5B%7B%22name%22%3A%22%22%2C%22hint%22%3A%22time%22%2C%22dir%22%3A%22DESC%22%2C%22default%22%3Atrue%7D%5D%7D%2C%22format%22%3A2%7D%5D%2C%22range%22%3A%7B%22from%22%3A%22now-1h%22%2C%22to%22%3A%22now%22%7D%2C%22panelsState%22%3A%7B%22logs%22%3A%7B%22sortOrder%22%3A%22Descending%22%7D%7D%2C%22compact%22%3Afalse%7D%7D&orgId=1) - What changes to this metric should prompt a rollback: `/v1/classify` requests are failing - Metric: Sentry Errors - Location: https://new-sentry.gitlab.net/organizations/gitlab/discover/results/?field=environment&field=release&project=39&statsPeriod=1h - What changes to this metric should prompt a rollback: Errors in Sentry for HTTP Router service - Metric: http-router Service RPS - Requests per Second - Location: [http-router Service RPS - Requests per Second](https://dashboards.gitlab.net/d/http-router-main/http-router3a-overview?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-ops&var-environment=gprd&var-shard=$__all&viewPanel=panel-2433781180) - What changes to this metric should prompt a rollback: Significant change in RPS - Metric: http-router Service Error Ratio - Location: [http-router Service Error Ratio](https://dashboards.gitlab.net/d/http-router-main/http-router3a-overview?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-ops&var-environment=gprd&var-shard=$__all&viewPanel=panel-3495312364) - What changes to this metric should prompt a rollback: Significant change in Error Ratio - Metric: web Service RPS - Requests per Second - Location: [web Service RPS - Requests per Second](https://dashboards.gitlab.net/d/web-main/web3a-overview?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment=gprd&var-stage=main&viewPanel=panel-537181794) - What changes to this metric should prompt a rollback: Significant change in RPS - Metric: web Service Error Ratio - Location: [web Service Error Ratio](https://dashboards.gitlab.net/d/web-main/web3a-overview?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-gitlab-gprd&var-environment=gprd&var-stage=main&viewPanel=panel-1806708210) - What changes to this metric should prompt a rollback: Significant change in Error Ratio - Metric: topology-rest: HTTP Performance - Location: [topology-rest: HTTP Performance](https://dashboards.gitlab.net/d/topology-rest-http-performance/topology-rest3a-http-performance?orgId=1&from=now-1h&to=now&timezone=utc&var-PROMETHEUS_DS=mimir-runway&var-environment=gprd) - What changes to this metric should prompt a rollback: Latency or saturation hit the SLI threshold - Metric: Production - Topology Service Cache Hit Ratio - Location: [CloudFlare Visualisation](https://dash.cloudflare.com/852e9d53d0f8adbd9205389356f2303d/observability/queries/xo7utwtnb51ygix2gt2qeeui/visualizations?filters=%5B%7B%22key%22%3A%22%24metadata.service%22%2C%22operation%22%3A%22eq%22%2C%22value%22%3A%22production-gitlab-com-cells-http-router%22%2C%22type%22%3A%22string%22%7D%5D&filterCombination=%22and%22&calculations=%5B%7B%22operator%22%3A%22count%22%7D%5D&groupBys=%5B%7B%22type%22%3A%22string%22%2C%22value%22%3A%22cache%22%7D%5D&orderBy=%7B%22value%22%3A%22count%22%2C%22order%22%3A%22desc%22%2C%22limit%22%3A10%7D&timeframe=1h&conditions=%7B%7D&conditionCombination=%22and%22&alertTiming=%7B%22interval%22%3A300%2C%22window%22%3A900%2C%22timeBeforeFiring%22%3A600%2C%22timeBeforeResolved%22%3A600%7D) - What changes to this metric should prompt a rollback: Should not be significantly more hits than misses. Non-blocking issue, no rollback required. - Metric: Increase in non 200 status requests. - Location: https://dashboards.gitlab.net/goto/dfg74twby1og0d?orgId=1 - What changes to this metric should prompt a rollback: Significant change in non 200 errors count. - Metric: Total number of logins - Location: https://log.gprd.gitlab.net/app/lens#/edit/3478b229-2038-4c9c-84bc-19475d6e4c5b?_g=(filters:!(),refreshInterval:(pause:!t,value:60000),time:(from:now-1h/h,to:now)) - What changes to this metric should prompt a rollback: Significant change in login counts per minute, that means users are forced to logout.