Being able to optionally disable logging of "GET /status" in the access logs #7276
Replies: 4 comments 1 reply
-
We have Kong running in kubernetes with datadog and an ALB load-balancing(multi-region so effectively three). All 5 are hitting this endpoint to generate 50 requests per minute per kong instance (we have 2) |
Beta Was this translation helpful? Give feedback.
-
We would like to have this too as the status log entries are irrelevant for us and just generates costs. |
Beta Was this translation helpful? Give feedback.
-
Its even more than this if you are running on kubernetes. As then you have the probes hitting the endpoints as well. Generating millions of logs. Really sad that both the issue that started this discussion and this discussion has been completely ignored for what 5 years now. |
Beta Was this translation helpful? Give feedback.
-
Kong Gateway does not provide a way to filter individual access log entries, but you can use a custom plugin to generate the access log, and implement your filtering logic there. Alternatively, you can use a custom nginx template and configure conditional logging there: In the http block:
In the server block:
|
Beta Was this translation helpful? Give feedback.
-
Kong provides a
GET /status
endpoint to check for the status of Kong, which should be optionally disabled since it creates lots of noise in the access logs when a client is making frequent requests to it.Beta Was this translation helpful? Give feedback.
All reactions