bernardodemarco commented on PR #8924: URL: https://github.com/apache/cloudstack/pull/8924#issuecomment-2062446576
@DaanHoogland, thanks for your review! As logging standards in CloudStack are still under discussion (#8746), I'd rather keep logging the exceptions stacktraces at the `error` level. Honestly, I do not see the point in turning off the stacktraces at the `error` level. For operators that have a minimum software development background, the stacktraces can be a useful way to perform troubleshooting processes. On the other hand, if the operator has no knowledge of development, he might not understand the stacktraces, and that is fine, causing no harm. Besides that, following along with what you've proposed in #8746, what happens when the operator chooses to turn the stacktraces down by setting the logs level to `error`? Are all exception logs be lost, since they are gonna be at `debug` level? If so, the difficulty of performing troubleshootings would increase significantly, as some errors/problems might be difficult to reproduce. Honestly, I'm looking forward to see the outcome of the #8746 discussion and I commit myself to participate on it. However, as I've mentioned before, I'd rather keep the proposed changes related to the stacktraces at the `error` level the way they are. -- 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. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
