From @Nuria's email on Analytics internal we should:
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| Prune old druid request logs | operations/puppet | production | +15 -1 | |
| Add cron to prune old druid indexer logs | operations/puppet | production | +8 -0 |
To be clear indexing logs are present but just in one of the three machines. Pulling would need to be set up for application logs and indexing logs, specially application logs as they are full of heart beats.
Just asked in druid user group:
https://groups.google.com/forum/#!topic/druid-user/Lzi98rsSR0k
Change 344983 had a related patch set uploaded (by Ottomata):
[operations/puppet@production] Add cron to prune old druid indexer logs
Change 344983 merged by Ottomata:
[operations/puppet@production] Add cron to prune old druid indexer logs
Change 344990 had a related patch set uploaded (by Ottomata):
[operations/puppet@production] Prune old druid request logs
Change 344990 merged by Ottomata:
[operations/puppet@production] Prune old druid request logs
I went ahead and just added the cron jobs. If we learn of a way to use log4j for the requests logs, we can revisit this then.