[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: SLING-4114-jsedding-v2.patch Patch without API changes. However, the date/time is omitted from the RPT messages. Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: SLING-4114-jsedding-v2.patch Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: (was: SLING-4114-jsedding-v2.patch) Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding-v2.patch, SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SLING-4114) Reduce amount of log output from RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Julian Sedding updated SLING-4114: -- Attachment: SLING-4114-jsedding.patch Patch implementing above suggestions. Reduce amount of log output from RequestProgressTrackerLogFilter - Key: SLING-4114 URL: https://issues.apache.org/jira/browse/SLING-4114 Project: Sling Issue Type: Improvement Components: Engine Affects Versions: Engine 2.3.6 Reporter: Julian Sedding Attachments: SLING-4114-jsedding.patch The RequestProgressTracker currently logs each RPT message as a separate log entry. Considering the potentially large number of log entries this can add significantly to the size of log files and the I/O involved. By logging all RPT messages as a single log entry, the overhead can be reduced. In addition, filtering by extension and request duration (min/max) can further reduce the log size (and simplify analysis). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
