The documentation just throw the enduser to do logback for debug logging rotation and file managing. However there is not enough information how to do this such that one can make use with AM setting of where to get the debug path or if AM default debug log level.
In fact if one goes to logback, it seems that doing much there may be some hardcoding in the logback. This is not appropriate for the supportability of this. There is the use of logback in groovy where one may be able to integrate to get AM default log level and even path so that if one administer things it will be easier for people to manage this
1. There is no public interface of API (in LogBack groovy) to get AM internal (unless this is fine to expose these internal)
2. There is no logback.groovy mentioned as this will help with these integration
3. AM internally seems to use this logback.groovy but this information (or what this is is not exposed)
Either the above could be RFE or docs
Imagine you are asked to do a custom logback to maintain the old AM log file structure with rotation and have seamlessly also startup with the Debug logging set in the Admin UI (like message, error, warning) and follows the settings in the AM for each instance where the debug log is. (all without doing any hardcoding of paths but using information from AM).
- Undocumented hack