Skip to content

Allow Suppression of Logs from Healthcheck Endpoints #66

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
lzettel opened this issue Feb 11, 2025 · 1 comment
Open

Allow Suppression of Logs from Healthcheck Endpoints #66

lzettel opened this issue Feb 11, 2025 · 1 comment

Comments

@lzettel
Copy link

lzettel commented Feb 11, 2025

Description

We have a Rails application running with the default health check implemented at /up, and we are constantly receiving logs like this:

{"time":"2025-02-11T06:48:36.879509079Z","level":"INFO","msg":"Request","path":"/up","status":200,"dur":7,"method":"GET","req_content_length":0,"req_content_type":"","resp_content_length":73,"resp_content_type":"text/html; charset=utf-8","remote_addr":"x.x.x.x:xxxx","user_agent":"kube-probe/1.28","cache":"miss","query":""}

These logs are generated by liveness probes and do not provide useful insights while adding unnecessary noise to our logs.

Rails already provides an option to silence these kinds of logs:

  # Prevent health checks from clogging up the logs.
  config.silence_healthcheck_path = '/up'

Feature Request

It would be nice to have the ability to suppress logs for specific endpoints, such as /up. The endpoint(s) could be set with an ENV.

Thanks in advance for your time and effort in considering this request!

@brotich
Copy link

brotich commented Apr 27, 2025

this looks like duplicate of #49 which already has PR here #50

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants