Radeity commented on issue #13017: URL: https://github.com/apache/dolphinscheduler/issues/13017#issuecomment-1328659415
Good idea! One humble suggestion that **different log level** contributes to failure diagnosis differently, level of `error`, `warn`(high level) may contribute more than `info`, `debug`, `trace`(low level). Intuitively, it should better **keep more higher level log** and clean lower level log first when reach the maximum capacity of remote storage. Maybe we can separate different level of logs when flushing and support [log aggregation](https://bambrow.com/20221021-yarn-log-aggregation/#more) when reading logs like Yarn. WDYT? -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
