You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2019/04/03 00:12:26 UTC
[GitHub] [incubator-druid] egor-ryashin edited a comment on issue #7362:
Principles for choosing logging severity
egor-ryashin edited a comment on issue #7362: Principles for choosing logging severity
URL: https://github.com/apache/incubator-druid/issues/7362#issuecomment-479266133
I don't agree with dropping trace or debug logging, actually.
The counterargument usually those can/should be introduced during testing only, well, sometimes there's a bug in production which is not reproduced in the testing environment. If there's no debug/trace coded at all, one has to introduce the logging and upgrade the production cluster.
In my experience, if debug/trace logging doesn't help to find out where the root cause is, they at least help to identify where it is not.
About INFO, just wonder if segment load action should be logged assuming you can get the segment location using HTTP API?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org