-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Add configuration property to disable http access log for certain routes #13377
Comments
/cc @geoand |
I think this makes sense. |
y. A similar mechanism exists in micrometer to exclude urls. I don't know that I would exclude them by default. It can be the easiest first check that things are working properly (even before your endpoint works). |
Probably should be a follow on from #13144 to make it easier as it can be anything under the endpoint prefix is ignored |
I don't see anything in #13144 that talks about configuring logging for non application endpoints. |
Hello to all. Is there any update on this ? Is this possible now ? |
Any chance there'd be an example for path such as |
When you take a look at the code it is just a regex. For your example it would be I know this reply is late but I want to add it in case someone else is searching for an example (maybe it could be added to the documentation / tutorials). |
Documentation enhancements are always welcome! |
Description
Quarkus provides a way to log the http calls being made to it via the config property
quarkus.http.access-log.enabled
and this is just fine. However, in a kubernetes environment, this usually means that all the liveness and readiness probes also get logged which makes the logs very messy (IMO). So it would be great if there was a property likequarkus.http.access-log.disabled-routes
where we specify which routes will not be logged and for good measure, this can be defaulted to routes like /health, /health/live, /health/ready and /metrics.Implementation ideas
The text was updated successfully, but these errors were encountered: