We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We have a Rails application running with the default health check implemented at /up, and we are constantly receiving logs like this:
/up
{"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'
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!
The text was updated successfully, but these errors were encountered:
this looks like duplicate of #49 which already has PR here #50
Sorry, something went wrong.
No branches or pull requests
Description
We have a Rails application running with the default health check implemented at
/up
, and we are constantly receiving logs like this: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:
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!
The text was updated successfully, but these errors were encountered: