Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-67203

JIRA Development Status Logging Improvements

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Application Links
    • None
    • 0
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      Problem Definition:

      In any case where there is a lot of Development Tools information is related to a JIRA ticket such as; builds, commit, PR, or environtments, JIRA would throw the stack trace below:

      2018-04-04 00:15:00,850 devstatus.applink:thread-1 WARN flarsson 528x7987130x1 asdacas xxx.xx.x.xx,xxx.xx.x.xxx,127.0.0.1 /rest/dev-status/1.0/issue/summary [c.a.j.p.d.p.source.cache.CachingProviderDecorator] JSON for issue 47781 is too big. It's size is 38413
      2018-04-04 00:15:02,669 devstatus.applink:thread-1 WARN flarsson 528x7987130x1 asdacas xxx.xx.x.xx,xxx.xx.x.xxx,127.0.0.1 /rest/dev-status/1.0/issue/summary [c.a.j.p.d.p.source.cache.CachingProviderDecorator] JSON for issue 45796 is too big. It's size is 33928
      2018-04-04 00:15:07,607 http-nio-8080-exec-3 ERROR anonymous 14x8806467x3 asdacas xxx.xx.x.xx,xxx.xx.x.xxx,127.0.0.1 /rest/dev-status/1.0/webhooks/update-summary [c.a.p.r.c.error.jersey.ThrowableExceptionMapper] Uncaught exception thrown by REST service: com.atlassian.jira.entity.property.FieldTooLongJsonPropertyException: Value specified for field 'json' is too long: 32771 > 32768
      com.google.common.util.concurrent.UncheckedExecutionException: com.atlassian.jira.entity.property.FieldTooLongJsonPropertyException: Value specified for field 'json' is too long: 32771 > 32768
      

      This is causing unnecessary noise in the logs and could cause misunderstanding to the Admin as one of it is being mentioned as ERROR.

      Suggested Solution:

      To set all the stack trace as WARN or to have it removed completely as it is harmless.

      Notes.

      • The stack trace was actually thrown due to the code has a condition where the JSON body is more than 32kb, it will throw such stack trace in the logs. It is not due to the value has reached the Database Column limit.
      • While there is an ERROR, the information itself is inserted into the database.
      • These stack traces are harmless as the information is inserted into the database.
      • To reduce the logging level which is to exclude the stack trace above to be written, the packages that the logging level that can be adjusted is:
        com.atlassian.jira.plugin.devstatus.provider.source.cache.CachingProviderDecorator
        com.atlassian.plugins.rest.common.error.jersey
        com.atlassian.jira.entity.property
        

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated: