You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2014/11/18 10:20:36 UTC
[jira] [Closed] (SLING-4114) Compact and more specific logs from
RequestProgressTrackerLogFilter
[ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-4114.
-----------------------------------
> Compact and more specific logs 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.8
> Reporter: Julian Sedding
> Assignee: Bertrand Delacretaz
> Fix For: Engine 2.3.10
>
> 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)