Uploaded image for project: 'Grouper'
  1. Grouper
  2. GRP-4467

Add property for GrouperLoaderLog jobs not to log at DEBUG

    XMLWordPrintable

Details

    • New Feature
    • Resolution: Unresolved
    • Minor
    • None
    • 2.6.7
    • daemon
    • None

    Description

      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.

      Attachments

        Activity

          People

            chris.hyzer@at.internet2.edu Chris Hyzer (upenn.edu)
            chad.redman.3@at.internet2.edu Chad Redman
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: