Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-5373

Suppress WARN messages regarding SLA after a project has changed type from Service Desk to Business / Software

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • SLA
    • 4
    • 27
    • We collect Jira Service Desk 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.

      Summary

      WARN messages in logs regarding SLAs

      1. Create a new Service Desk project
        • SLAs should be created by default for this project
      2. Change the project type to Business or Software
      3. Tail the logs
      4. Access the SLA page of another Service Desk project

      The following will be seen in the logs

      2017-09-07 16:23:09,658 http-nio-7431-exec-3 WARN admin 983x481x1 1d8hks9 127.0.0.1 /rest/servicedesk/1/servicedesk/agent/SDA/sla/consistencydata [c.a.s.i.sla.searcher.OutdatedSlaQueryGenerator] Time metric with name Time to first response and id 4 not associated with any service desk project : Errors: {}
          Error Messages: [The Service Desk you are trying to view does not exist.]
      2017-09-07 16:23:09,662 http-nio-7431-exec-3 WARN admin 983x481x1 1d8hks9 127.0.0.1 /rest/servicedesk/1/servicedesk/agent/SDA/sla/consistencydata [c.a.s.i.sla.searcher.OutdatedSlaQueryGenerator] Time metric with name Time to resolution and id 3 not associated with any service desk project : Errors: {}
          Error Messages: [The Service Desk you are trying to view does not exist.]
      2017-09-07 16:23:10,157 http-nio-7431-exec-7 WARN admin 983x488x1 1d8hks9 127.0.0.1 /rest/servicedesk/1/servicedesk/agent/SDA/sla/metrics [c.a.s.i.sla.searcher.OutdatedSlaQueryGenerator] Time metric with name Time to first response and id 4 not associated with any service desk project : Errors: {}
          Error Messages: [The Service Desk you are trying to view does not exist.]
      2017-09-07 16:23:10,159 http-nio-7431-exec-7 WARN admin 983x488x1 1d8hks9 127.0.0.1 /rest/servicedesk/1/servicedesk/agent/SDA/sla/metrics [c.a.s.i.sla.searcher.OutdatedSlaQueryGenerator] Time metric with name Time to resolution and id 3 not associated with any service desk project : Errors: {}
          Error Messages: [The Service Desk you are trying to view does not exist.]
      

      The project type is intentionally changed, so this message is redundant.

      Suggestion

      Suppress or remove this WARN message when a Service Desk project changed type to Business/Software

      Note

      This is different from JSDSERVER-5117. The name and id of the SLA is clearly stated in the logs for this.

      Workaround

      Navigate to the logging and profiling page and set the logging level to Error for the following package com.atlassian.servicedesk.internal

          Form Name

            [JSDSERVER-5373] Suppress WARN messages regarding SLA after a project has changed type from Service Desk to Business / Software

            Is there a way to clean up the SLA's to reduce the impact on performance?  If not, I would add to this feature some means if identifying orphaned SLAs and cleaning them up.

            Brian Cummings added a comment - Is there a way to clean up the SLA's to reduce the impact on performance?  If not, I would add to this feature some means if identifying orphaned SLAs and cleaning them up.

            I'm seeing these WARN messages in our test environment. In our case it looks like the SLA ID's referenced in the WARN messages are from projects that have been deleted from the test environment. It seems that even through the project is deleted the SLA metrics for that project remain in the system and database. This then flags as a WARN message in the logs for any new issues entered in Service Desk regardless of the project. 

            I would like to suggest that along with the ability to suppress the WARN messages in the logs you add functionality to better clean up these old SLA metrics when a project is deleted.   

             

             

            Weston Rossborough added a comment - I'm seeing these WARN messages in our test environment. In our case it looks like the SLA ID's referenced in the WARN messages are from projects that have been deleted from the test environment. It seems that even through the project is deleted the SLA metrics for that project remain in the system and database. This then flags as a WARN message in the logs for any new issues entered in Service Desk regardless of the project.  I would like to suggest that along with the ability to suppress the WARN messages in the logs you add functionality to better clean up these old SLA metrics when a project is deleted.       

              Unassigned Unassigned
              ywoo Yit Wei
              Votes:
              39 Vote for this issue
              Watchers:
              27 Start watching this issue

                Created:
                Updated: