Excessive logging from unicorn healthcheck
Summary
Every time the healthcheck runs for the unicorn container. The healthcheck gets redirected, and is logged.
==> /var/log/gitlab/production.log <==
Started GET "/" for 127.0.0.1 at 2019-05-07 00:09:32 +0000
Processing by RootController#index as HTML
Redirected to http://localhost/users/sign_in
Filter chain halted as :redirect_unlogged_user rendered or redirected
Completed 302 Found in 7ms (ActiveRecord: 0.6ms)
==> /var/log/gitlab/production_json.log <==
{"method":"GET","path":"/","format":"html","controller":"RootController","action":"index","status":302,"duration":9.08,"view":0.0,"db":0.56,"location":"http://localhost/users/sign_in","time":"2019-05-07T00:09:32.975Z","params":[],"remote_ip":"127.0.0.1","user_id":null,"username":null,"ua":null,"queue_duration":null,"correlation_id":"e8b0affa-f67b-4aa0-89b0-b9152b429d1d"}
Steps to reproduce
Bring up cluster, turn off account creation, require sign in.
Configuration used
(Please provide a sanitized version of the configuration used wrapped in a code block (```yaml))
(Paste sanitized configuration here)
Current behavior
Extraneous logging for healthcheck endpoints
Expected behavior
lower levels of logging, perhaps just the access log, and not the debug logging
Versions
- Chart: v1.8.4
- Platform:
- Self-hosted: kubeadm
- Kubernetes: (
kubectl version
)- Client: v1.14.1
- Server: v1.14.1
- Helm: (
helm version
)- Client: v2.13.1
- Server: v2.13.1
Relevant logs
(Please provide any relevate log snippets you have collected, using code blocks (```) to format)
Edited by Wei K Huang