:arrow_up_small: Re-written 2022-10-26 following [a support ticket](https://gitlab.zendesk.com/agent/tickets/338993) on this topic.
Do you perform any sort of monitoring of Sidekiq? [Reding the impact statement](https://gitlab.com/gitlab-org/gitlab/-/issues/347509#affected-topology), there are three endpoints which are now split across two different ports:
Do you perform any sort of monitoring of Sidekiq? [Reading the impact statement](https://gitlab.com/gitlab-org/gitlab/-/issues/347509#affected-topology), there are three endpoints which are now split across two different ports:
> /metrics are now served by a dedicated server process, not an individual worker.
> /readiness and /liveness continue to be served by an in-worker HTTP server.
> - /metrics are now served by a dedicated server process, not an individual worker.
> - /readiness and /liveness continue to be served by an in-worker HTTP server.
From 15.0, the defaults (`# sidekiq['health_checks_listen_port'] = 8092`) indicate that the additional port was added for `/readiness` and `/liveness`, with the original port being the [default for Prometheus](https://gitlab.com/gitlab-org/omnibus-gitlab/blob/15.4.0+ee.0/files/gitlab-config-template/gitlab.rb.template#L1068):
