We use a custom GRAYLOG_REST_LISTEN_URI with a different path than /api (e.g. http://0.0.0.0:9000/rest_api) in this case the healthcheck always marks the container as unhealthy because it cannot find the api under /api and graylog responds with a 404 status code for http://0.0.0.0:9000/api (at least since the upgrade to 2.5)
This pull request fixes the healthcheck to also consider a custom path specified in the GRAYLOG_REST_LISTEN_URI and rest_listen_uri variables.
We use a custom GRAYLOG_REST_LISTEN_URI with a different path than /api (e.g. http://0.0.0.0:9000/rest_api) in this case the healthcheck always marks the container as unhealthy because it cannot find the api under /api and graylog responds with a 404 status code for http://0.0.0.0:9000/api (at least since the upgrade to 2.5)
This pull request fixes the healthcheck to also consider a custom path specified in the GRAYLOG_REST_LISTEN_URI and rest_listen_uri variables.
Info @wt-io-it