Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'doc/administration/sidekiq_health_check.md')
-rw-r--r--doc/administration/sidekiq_health_check.md61
1 files changed, 7 insertions, 54 deletions
diff --git a/doc/administration/sidekiq_health_check.md b/doc/administration/sidekiq_health_check.md
index aaab2b7e086..3294eb663f2 100644
--- a/doc/administration/sidekiq_health_check.md
+++ b/doc/administration/sidekiq_health_check.md
@@ -1,58 +1,11 @@
---
-stage: Systems
-group: Distribution
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
+redirect_to: 'sidekiq/sidekiq_health_check.md'
+remove_date: '2022-11-11'
---
-# Sidekiq Health Check **(FREE SELF)**
+This document was moved to [another location](sidekiq/sidekiq_health_check.md).
-GitLab provides liveness and readiness probes to indicate service health and
-reachability to the Sidekiq cluster. These endpoints
-[can be provided to schedulers like Kubernetes](https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/)
-to hold traffic until the system is ready or restart the container as needed.
-
-The health check server can be set up when [configuring Sidekiq](sidekiq.md).
-
-## Readiness
-
-The readiness probe checks whether the Sidekiq workers are ready to process jobs.
-
-```plaintext
-GET /readiness
-```
-
-If the server is bound to `localhost:8092`, the process cluster can be probed for readiness as follows:
-
-```shell
-curl "http://localhost:8092/readiness"
-```
-
-On success, the endpoint returns a `200` HTTP status code, and a response like the following:
-
-```json
-{
- "status": "ok"
-}
-```
-
-## Liveness
-
-Checks whether the Sidekiq cluster is running.
-
-```plaintext
-GET /liveness
-```
-
-If the server is bound to `localhost:8092`, the process cluster can be probed for liveness as follows:
-
-```shell
-curl "http://localhost:8092/liveness"
-```
-
-On success, the endpoint returns a `200` HTTP status code, and a response like the following:
-
-```json
-{
- "status": "ok"
-}
-```
+<!-- This redirect file can be deleted after <2022-11-11>. -->
+<!-- Redirects that point to other docs in the same project expire in three months. -->
+<!-- Redirects that point to docs in a different project or site (link is not relative and starts with `https:`) expire in one year. -->
+<!-- Before deletion, see: https://docs.gitlab.com/ee/development/documentation/redirects.html -->