Skip to content
Snippets Groups Projects
Commit ae6d966e authored by Matthias Käppler's avatar Matthias Käppler :two:
Browse files

Update Sidekiq health check docs

This removes the deprecation notice, since some
behavior was removed with 15.0.
parent 551e9fc6
No related branches found
No related tags found
1 merge request!86234Update Sidekiq health check docs
Pipeline #527763181 passed
......@@ -192,12 +192,8 @@ To configure the metrics server:
## Configure health checks
If you use health check probes to observe Sidekiq,
you can set a separate port for health checks.
Configuring health checks is only necessary if there is something that actually probes them.
For more information about health checks, see the [Sidekiq health check page](sidekiq_health_check.md).
To enable health checks for Sidekiq:
If you use health check probes to observe Sidekiq, enable the Sidekiq health check server.
To make health checks available from `localhost:8092`:
1. Edit `/etc/gitlab/gitlab.rb`:
......@@ -207,16 +203,14 @@ To enable health checks for Sidekiq:
sidekiq['health_checks_listen_port'] = "8092"
```
NOTE:
If health check settings are not set, they default to the metrics exporter settings.
This default is deprecated and is set to be removed in [GitLab 15.0](https://gitlab.com/gitlab-org/gitlab/-/issues/347509).
1. Reconfigure GitLab:
```shell
sudo gitlab-ctl reconfigure
```
For more information about health checks, see the [Sidekiq health check page](sidekiq_health_check.md).
## Configure LDAP and user or group synchronization
If you use LDAP for user and group management, you must add the LDAP configuration to your Sidekiq node as well as the LDAP
......
......@@ -21,8 +21,7 @@ The readiness probe checks whether the Sidekiq workers are ready to process jobs
GET /readiness
```
If you set Sidekiq's address as `localhost` and port as `8092`,
here's an example request:
If the server is bound to `localhost:8092`, the process cluster can be probed for readiness as follows:
```shell
curl "http://localhost:8092/readiness"
......@@ -44,8 +43,7 @@ Checks whether the Sidekiq cluster is running.
GET /liveness
```
If you set Sidekiq's address as `localhost` and port as `8092`,
here's an example request:
If the server is bound to `localhost:8092`, the process cluster can be probed for liveness as follows:
```shell
curl "http://localhost:8092/liveness"
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment