Merge branch 'use-prometheus-metrics' into 'master'

Use prometheus metrics for monitoring geo numbers

See merge request gitlab-com/migration!195

.gitlab/issue_templates/failover.md

@@ -290,10 +290,9 @@ Running CI jobs will no longer be able to push updates. Jobs that complete now m
     * The loop should be stopped once sidekiq is shut down
     * Wait for `--> Status: PROCEED`
 1. [ ] 🐺 {+ Coordinator +}: Wait for repository verification on the **primary** to complete
-    * Staging: https://staging.gitlab.com/admin/geo_nodes - `staging.gitlab.com` node
-    * Production: https://gitlab.com/admin/geo_nodes - `gitlab.com` node
-    * Expand the `Verification Info` tab
-    * Wait for the number of `unverified` repositories to reach 0
+    * Staging: https://performance.gitlab.net/d/000000286/gcp-failover-azure?orgId=1&var-environment=stg
+    * Production: https://performance.gitlab.net/d/000000286/gcp-failover-azure?orgId=1&var-environment=prd
+    * Wait for the number of `unverified` repositories and wikis to reach 0
     * Resolve any repositories that have `failed` verification
 1. [ ] 🐺 {+ Coordinator +}: Wait for all Sidekiq jobs to complete on the primary
     * Staging: https://staging.gitlab.com/admin/background_jobs
@@ -337,9 +336,10 @@ state of the secondary to converge.
     * If failures appear, see Rails console commands to resync repos/wikis: https://gitlab.com/snippets/1713152
     * On staging, this may not complete
 1. [ ] 🐺 {+ Coordinator +}: Wait for all repositories and wikis to become verified
-    * Press "Verification Information"
+    * Staging: https://dashboards.gitlab.net/d/YoKVGxSmk/gcp-failover-gcp?orgId=1&var-environment=gstg
+    * Production: https://dashboards.gitlab.net/d/YoKVGxSmk/gcp-failover-gcp?orgId=1&var-environment=gprd
     * Wait for "repositories verified" and "wikis verified" to reach 100% with 0 failures
-    * You can use `sudo gitlab-rake geo:status` instead if the UI is non-compliant
+    * You can also use `sudo gitlab-rake geo:status`
     * If failures appear, see https://gitlab.com/snippets/1713152#verify-repos-after-successful-sync for how to manually verify after resync
     * On staging, verification may not complete
 1. [ ] 🐺 {+ Coordinator +}: In "Sync Information", wait for "Last event ID seen from primary" to equal "Last event ID processed by cursor"