-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
[Feature request]: Allow disabling of query logs #225
Comments
You can disable the query log, just remove |
Thank you, wasn't clear from documentation to me. Closing. |
In example configuration there's no query log section, but docker logs all queries. Do I miss something? I use version 0.14. |
Ok, I think, there is a misunderstanding: If |
Yes, the idea is to allow intentional disabling of query log.
Not sure how many users need this but it would obviously increase privacy.
…On Fri, Jun 25, 2021 at 15:15, Dimitri Herzog ***@***.***> wrote:
Ok, I think, there is a misunderstanding: If queryLog is enabled, blocky logs each request with response in a CSV file. If queryLog is disabled, blocky logs only to stdout. The only way to disable it is to increase the log Level (to warn for example)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, [view it on GitHub](#225 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/AAP2C7VZ6UTM45T2MOQOEM3TUR6PBANCNFSM47JUYUIA).
|
ok, I know what you mean. I think, it would make sense not to log each request with detailed information on info log level (which is default). I would leave detailed logging (is useful for debugging or investigation of dns problems), but maybe use some kind of "special" logger which is disabled by default or just on debug level. |
Solution: |
This is a feature request.
Would be nice to have query log completely disabled for better privacy.
Query log can be enabled by default as it is now but should be optionally disabled with a change to a configuration.
The text was updated successfully, but these errors were encountered: