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

SubjectSourceCache.logStats() diagnostics should log at DEBUG level, not WARN

    XMLWordPrintable

Details

    • Improvement
    • Resolution: Fixed
    • Minor
    • 4.0.0
    • 2.4.0.patch
    • API
    • None

    Description

      grouper-daemon;grouper_error.log;2023-01-24T19:29:30,253: [Thread-26] WARN  SubjectSourceCache.logStats(640) - [] - date: 2023_01_24, subjectsInCache: 11161, cacheKeysIdsIdentifiers: 11162, cacheHitsIndividual: 3, microsPerCacheHit: 56, cacheMissesIndividual: 11162, microsPerCacheMissIndividual: 25065, cacheMissesForList: 0, microsPerCacheMissForList: 0, cacheMissesResolved: 11134, cacheMissesUnresolved: 28, cacheRemoves: 0, cacheHitsSinceLastRetrieve: 3, cacheHitsTotalOfItemsInCache: 11164, cacheSizeSubjectsResolved: 11133, cacheSizeSubjectsUnresolved: 28, numberOfSubjectsRefreshedInBackground: 0, refreshQueriesInBackground: 0, microsPerBackgroundRefreshQuery: 0, cacheRefreshesTotalOfItemsInCache: 11161, itemsWithNoAccessSinceLastRefresh: 11160, itemsWith1AccessSinceLastRefresh: 1, itemsWith3AccessSinceLastRefresh: 1, itemsWith10AccessSinceLastRefresh: 0, itemsWith20AccessSinceLastRefresh: 0, itemsWith1Refresh: 11161, itemsWith3Refresh: 0, itemsWith10Refresh: 0, itemsWith20Refresh: 0, itemsWith50Refresh: 0, itemsWith1AccessTotal: 11161, itemsWith3AccessTotal: 1, itemsWith10AccessTotal: 0, itemsWith20AccessTotal: 0, itemsWith50AccessTotal: 0
      

      This information is really debug-level. Probably doesn't warrant warn-level, if users want to limit the amount of excess logging.

      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:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: