Closed jdries closed 4 months ago
you mean EJR related logs happening from the job tracker cron job that show up in batch job logs seen by end users?
@soxofaan @jdries Is this a change in log4j or in the code?
on cdse we solved it by putting EJR logs in a separate index, which is not included when retrieving logs. This avoids that we have to reduce all EJR logging, and also allowed to set lower retention time on job tracker index. I however don't have an opinion on the best solution really, for me the most urgent thing is that users really shouldn't see this, as it reduces usability of logs quite a bit.
Indeed, I would fix this by piping the Terrascope job tracker logs to a dedicated index, like we do on CDSE
I think this one is done and can be closed
ejr logging on cdse got reduced some time ago, but this solution does not apply to terrascope (yet) we should do the same there.