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

As a Service Desk Admin I would like to be able to disable the SLA Audit Log so that I can improve performance and stability of Jira Service Desk Server

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 4.22.0
    • SLA
    • None
    • 33
    • 2
    • 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.

      Atlassian Update – 1 Feb 2022

      Hi everyone,

      Thank you for your interest in this issue.

      Jira Service Management 4.22 will include a new SLA configuration interface. This includes settings for SLA debug log events. As a Jira administrator, you can decide how you want the SLA debug log to be cleaned up. You can also select how often the events will be deleted from the database, and whether or not you want SLA logging to be enabled.

      Kind regards,

      Charlie Marriott
      Jira Service Management, Data Center & Server

      Problem Definition

      In Jira Service Desk Server 3.4.1 an SLA Audit Log was introduced for troubleshooting SLAs. This audit log can grow to huge sizes in the database, so a cleanup job was introduced(https://jira.atlassian.com/browse/JSDSERVER-5266). This cleanup job helps to keep the size of the database tables smaller, but can still allow the audit log to grow to large sizes and the job itself can become very resource intensive and long running. This leads to a performance impact due to the SQL query used and a stability impact because the query can become long running(over 30 hours has been seen) and can block other database calls.

      Suggested Solution

      Provide a dark feature, or other configurable parameter, to completely disable the SLA Audit Log.

      Why this is important

      The tradeoff between the benefits of the SLA Audit Log and the impact it can create is something that may vary from instance to instance and should be configurable to best fit the use case for that instance.
      This is important because admins should be given the choice of whether to use the audit log feature or not.

      Workaround

       
      The closest thing to a workaround is to set a configuration setting in the database to reduce the number of days before an audit event is cleaned up. The default is 30 days and this can allow the tables to get too large, slowing down the cleanup job. If we reduce this to 1 day the tables will be kept much smaller and because they are smaller the cleanup job is able to complete much more quickly.

      The database property is:

      sd.sla.audit.log.cleanup.days

      Run the SQL query to determine the ID of the property in the database:

      SELECT * FROM propertyentry JOIN propertynumber ON propertyentry.ID=propertynumber.ID WHERE PROPERTY_KEY = "sd.sla.audit.log.cleanup.days";

      Then to modify this parameter from 30 to 1:

      UPDATE propertynumber SET propertyvalue=1 WHERE ID = <ID from above>;

      Related tickets:

            [JSDSERVER-5871] As a Service Desk Admin I would like to be able to disable the SLA Audit Log so that I can improve performance and stability of Jira Service Desk Server

            Murakami [Atlassian Support] made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 802971 ]
            Alex Stegani made changes -
            Description Original: {panel:title=Atlassian Update – 1 Feb 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Hi everyone,

            Thank you for your interest in this issue.

            Jira Service Management 4.22 will include a new SLA configuration interface. This includes settings for SLA debug log events. As a Jira administrator, you can decide how you want the SLA debug log to be cleaned up. You can also select how often the events will be deleted from the database, and whether or not you want SLA logging to be enabled.

            Kind regards,

            Charlie Marriott
            Jira Service Management, Data Center & Server
            {panel}
            h3. Problem Definition

            In Jira Service Desk Server 3.4.1 an SLA Audit Log was introduced for troubleshooting SLAs. This audit log can grow to huge sizes in the database, so a cleanup job was introduced(https://jira.atlassian.com/browse/JSDSERVER-5266). This cleanup job helps to keep the size of the database tables smaller, but can still allow the audit log to grow to large sizes and the job itself can become very resource intensive and long running. This leads to a performance impact due to the SQL query used and a stability impact because the query can become long running(over 30 hours has been seen) and can block other database calls.
            h3. Suggested Solution

            Provide a dark feature, or other configurable parameter, to completely disable the SLA Audit Log.
            h3. Why this is important

            The tradeoff between the benefits of the SLA Audit Log and the impact it can create is something that may vary from instance to instance and should be configurable to best fit the use case for that instance.
            This is important because admins should be given the choice of whether to use the audit log feature or not.
            h3. Workaround

             
            The closest thing to a workaround is to set a configuration setting in the database to reduce the number of days before an audit event is cleaned up. The default is 30 days and this can allow the tables to get too large, slowing down the cleanup job. If we reduce this to 1 day the tables will be kept much smaller and because they are smaller the cleanup job is able to complete much more quickly.

            The database property is:
            sd.sla.audit.log.cleanup.days

            Run the SQL query to determine the ID of the property in the database:
            {code:java}
            SELECT * FROM propertyentry JOIN propertynumber ON propertyentry.ID=propertynumber.ID WHERE PROPERTY_KEY = "sd.sla.audit.log.cleanup.days";
            {code}
            Then to modify this parameter from 30 to 1:
            {code:java}
            UPDATE propertynumber SET propertyvalue=1 WHERE ID = <ID from above>;
            {code}
            Related tickets:
            https://jira.atlassian.com/browse/JSDSERVER-5266
            https://jira.atlassian.com/browse/JSDSERVER-5719             		New: {panel:title=Atlassian Update – 1 Feb 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Hi everyone,

            Thank you for your interest in this issue.

            Jira Service Management 4.22 will include a new SLA configuration interface. This includes settings for SLA debug log events. As a Jira administrator, you can decide how you want the SLA debug log to be cleaned up. You can also select how often the events will be deleted from the database, and whether or not you want SLA logging to be enabled.

            Kind regards,

            Charlie Marriott
            Jira Service Management, Data Center & Server
            {panel}
            h3. Problem Definition

            In Jira Service Desk Server 3.4.1 an SLA Audit Log was introduced for troubleshooting SLAs. This audit log can grow to huge sizes in the database, so a cleanup job was introduced(https://jira.atlassian.com/browse/JSDSERVER-5266). This cleanup job helps to keep the size of the database tables smaller, but can still allow the audit log to grow to large sizes and the job itself can become very resource intensive and long running. This leads to a performance impact due to the SQL query used and a stability impact because the query can become long running(over 30 hours has been seen) and can block other database calls.
            h3. Suggested Solution

            Provide a dark feature, or other configurable parameter, to completely disable the SLA Audit Log.
            h3. Why this is important

            The tradeoff between the benefits of the SLA Audit Log and the impact it can create is something that may vary from instance to instance and should be configurable to best fit the use case for that instance.
            This is important because admins should be given the choice of whether to use the audit log feature or not.
            h3. Workaround

             
            The closest thing to a workaround is to set a configuration setting in the database to reduce the number of days before an audit event is cleaned up. The default is 30 days and this can allow the tables to get too large, slowing down the cleanup job. If we reduce this to 1 day the tables will be kept much smaller and because they are smaller the cleanup job is able to complete much more quickly.

            The database property is:
            {noformat}
            sd.sla.audit.log.cleanup.days
            {noformat}

            Run the SQL query to determine the ID of the property in the database:
            {code:sql}
            SELECT * FROM propertyentry JOIN propertynumber ON propertyentry.ID=propertynumber.ID WHERE PROPERTY_KEY = "sd.sla.audit.log.cleanup.days";
            {code}
            Then to modify this parameter from 30 to 1:
            {code:sql}
            UPDATE propertynumber SET propertyvalue=1 WHERE ID = <ID from above>;
            {code}
            Related tickets:
            * https://jira.atlassian.com/browse/JSDSERVER-5266
            * https://jira.atlassian.com/browse/JSDSERVER-5719
            Meriem Dhahak made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 670447 ]
            Marko Filipan made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 637421 ]
            Satej Mirpagar made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            UIS Original: 22 New: 33
            Charlie Marriott made changes -
            Description Original: h3. Problem Definition

            In Jira Service Desk Server 3.4.1 an SLA Audit Log was introduced for troubleshooting SLAs. This audit log can grow to huge sizes in the database, so a cleanup job was introduced(https://jira.atlassian.com/browse/JSDSERVER-5266). This cleanup job helps to keep the size of the database tables smaller, but can still allow the audit log to grow to large sizes and the job itself can become very resource intensive and long running. This leads to a performance impact due to the SQL query used and a stability impact because the query can become long running(over 30 hours has been seen) and can block other database calls.
            h3. Suggested Solution

            Provide a dark feature, or other configurable parameter, to completely disable the SLA Audit Log.
            h3. Why this is important

            The tradeoff between the benefits of the SLA Audit Log and the impact it can create is something that may vary from instance to instance and should be configurable to best fit the use case for that instance.
             This is important because admins should be given the choice of whether to use the audit log feature or not.
            h3. Workaround

             
             The closest thing to a workaround is to set a configuration setting in the database to reduce the number of days before an audit event is cleaned up. The default is 30 days and this can allow the tables to get too large, slowing down the cleanup job. If we reduce this to 1 day the tables will be kept much smaller and because they are smaller the cleanup job is able to complete much more quickly.

            The database property is:
             sd.sla.audit.log.cleanup.days

            Run the SQL query to determine the ID of the property in the database:
            {code:java}
            SELECT * FROM propertyentry JOIN propertynumber ON propertyentry.ID=propertynumber.ID WHERE PROPERTY_KEY = "sd.sla.audit.log.cleanup.days";
            {code}
            Then to modify this parameter from 30 to 1:
            {code:java}
            UPDATE propertynumber SET propertyvalue=1 WHERE ID = <ID from above>;
            {code}
            Related tickets:
             https://jira.atlassian.com/browse/JSDSERVER-5266
             https://jira.atlassian.com/browse/JSDSERVER-5719             		New: {panel:title=Atlassian Update – 1 Feb 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff}
            Hi everyone,

            Thank you for your interest in this issue.

            Jira Service Management 4.22 will include a new SLA configuration interface. This includes settings for SLA debug log events. As a Jira administrator, you can decide how you want the SLA debug log to be cleaned up. You can also select how often the events will be deleted from the database, and whether or not you want SLA logging to be enabled.

            Kind regards,

            Charlie Marriott
            Jira Service Management, Data Center & Server
            {panel}
            h3. Problem Definition

            In Jira Service Desk Server 3.4.1 an SLA Audit Log was introduced for troubleshooting SLAs. This audit log can grow to huge sizes in the database, so a cleanup job was introduced(https://jira.atlassian.com/browse/JSDSERVER-5266). This cleanup job helps to keep the size of the database tables smaller, but can still allow the audit log to grow to large sizes and the job itself can become very resource intensive and long running. This leads to a performance impact due to the SQL query used and a stability impact because the query can become long running(over 30 hours has been seen) and can block other database calls.
            h3. Suggested Solution

            Provide a dark feature, or other configurable parameter, to completely disable the SLA Audit Log.
            h3. Why this is important

            The tradeoff between the benefits of the SLA Audit Log and the impact it can create is something that may vary from instance to instance and should be configurable to best fit the use case for that instance.
            This is important because admins should be given the choice of whether to use the audit log feature or not.
            h3. Workaround

             
            The closest thing to a workaround is to set a configuration setting in the database to reduce the number of days before an audit event is cleaned up. The default is 30 days and this can allow the tables to get too large, slowing down the cleanup job. If we reduce this to 1 day the tables will be kept much smaller and because they are smaller the cleanup job is able to complete much more quickly.

            The database property is:
            sd.sla.audit.log.cleanup.days

            Run the SQL query to determine the ID of the property in the database:
            {code:java}
            SELECT * FROM propertyentry JOIN propertynumber ON propertyentry.ID=propertynumber.ID WHERE PROPERTY_KEY = "sd.sla.audit.log.cleanup.days";
            {code}
            Then to modify this parameter from 30 to 1:
            {code:java}
            UPDATE propertynumber SET propertyvalue=1 WHERE ID = <ID from above>;
            {code}
            Related tickets:
            https://jira.atlassian.com/browse/JSDSERVER-5266
            https://jira.atlassian.com/browse/JSDSERVER-5719
            Charlie Marriott made changes -
            Fix Version/s New: 4.22.0 [ 98292 ]
            Charlie Marriott made changes -
            Status Original: In Progress [ 3 ] New: Waiting for Release [ 12075 ]
            Charlie Marriott made changes -
            Status Original: Gathering Interest [ 11772 ] New: In Progress [ 3 ]

              Unassigned Unassigned
              bcohen@atlassian.com Brian Cohen (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              16 Start watching this issue

                Created:
                Updated:
                Resolved: