Analytics ProductEventListener Spamming Log

XMLWordPrintable

    • 179
    • Severity 3 - Minor
    • 130

      Summary

      The following log entry shows up a lot of times in the atlassian-confluence.log file when re-indexing the instance:

      WARN [Indexer: 2] [analytics.client.listener.ProductEventListener] rejectedExecution Analytics event not be processed (most likely due to too many events in queue for single-threaded event processor).

      Steps to Reproduce

      1. Rebuild the indices under Confluence admin > Content Indexing > Rebuild

      Expected Results

      1. Confluence will write only useful logs in the atlassian-confluence.log file.

      Actual Results

      The atlassian-confluence.log file is spammed with entries like this:

      WARN [Indexer: 2] [analytics.client.listener.ProductEventListener] rejectedExecution Analytics event not be processed (most likely due to too many events in queue for single-threaded event processor).

      Suggestion

      We should change this WARN to DEBUG level.

      Workaround

      1. Edit the <confluence-install-folder>/confluence/WEB-INF/classes/log4j.properties file
      2. Add these entries at the end of the file: 
        # Suppress analytics.client.listener.ProductEventListener WARN logs
log4j.logger.com.atlassian.analytics.client.listener.ProductEventListener=ERROR
      3. Save the file and restart your Confluence instance.
      Atlassian Update February 2018

      Thanks for your interest in this issue.

      We have made a number of improvements to this warning.
      In 6.0.1 we fixed a bug that causes the overflow of the ProductEventListener to put additional analytics events into the very same queue.
      In 6.5.0 we suppressed a full site re-index from sending analytics, thereby removing one of the major causes of spamming the application logs.
      We are holding simply changing the debug level by default as this is a valid warning.
      If you can post what feature/trigger caused you to receive this error message then we can better determine whether to suppress additional analytics events, increase the queue size, or reduce the frequency of the log message.

      Cheers,

      Confluence Product Management

            Assignee:
            Ragan Martinez
            Reporter:
            Eduardo Mallmann (Inactive)
            Votes:
            31 Vote for this issue
            Watchers:
            64 Start watching this issue

              Created:
              Updated:
              Resolved: