[GitHub] [druid] suneet-s commented on pull request #14094: Allow for Log4J to be configured for peons but still ensure console logging is enforced

["suneet-s (via GitHub)" <gi...@apache.org>]

suneet-s commented on PR #14094:
URL: https://github.com/apache/druid/pull/14094#issuecomment-1509995233

   > Because peon's log is saved to deep storage by middlemanagers, and the web-console provides a UI to show logs of tasks from deep storage, what's the motivation that users configure peon to write log to somewhere else?
   
   Users may not want to write the entire peon logs to another location since the logs are uploaded to deep storage eventually. 
   However, I can see a case where a Druid operator might want to expose a subset of the peon logs for consumption by non Druid experts. Here's an example I can think of
   
   * Some users may want to see ingestion progress logs, but the current peon logs are too detailed. Something like this would allow a Druid operator to configure ingestion progress logs to be written to a separate location with another appender while the entire set of logs is still uploaded to deep storage.


-- 
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-unsubscribe@druid.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org