GitHub user GutoVeronezi added a comment to the discussion: logging standards in CloudStack
I believe that adding an error message in `ERROR` followed by the stack trace in `DEBUG` is not so interesting. For instance, if we have the `INFO` level enabled and an exception occurs, we would not see it and would have to enable `DEBUG` and reproduce the situation to see the stack trace. Some situations are not so easy to reproduce; thus, we would lose track of the situation. Another point is that we would have to change the whole code base to comply with this standard. Furthermore, while in `DEBUG`, ACS prints a lot of logs; if one is concerned with the stack traces, however, still wants to keep the log level in `INFO`, it would not be possible. I understand @DaanHoogland's point about non-developer operators not wanting to see stack traces around the logs, and we can achieve that with less effort. Via the log pattern, Log4j allows us to define how many lines of the stack trace will be printed in the logs. Therefore, to address @DaanHoogland's point, this pattern could be defaulted to 0 stack trace lines. If desired, one would still be able to see the stack traces by changing the pattern, independently of the log level. This approach can address both use cases presented in a flexible and effortless fashion. GitHub link: https://github.com/apache/cloudstack/discussions/8746#discussioncomment-9168618 ---- This is an automatically sent email for users@cloudstack.apache.org. To unsubscribe, please send an email to: users-unsubscr...@cloudstack.apache.org
