Now that GrouperLoaderLog is being logged at debug level by default, it tends to clutter up the logs with maintenance and changelog jobs that run every minute. I think ideally you shouldn't have GrouperLoaderLog at debug level. But if you do, maybe it's because you want to know about a specific problem job, and not CHANGE_LOG_changeLogTempToChangeLog or basically any other CHANGE_LOG or MAINTENANCE job.