sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bertrand Delacretaz (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (SLING-4114) Compact and more specific logs from RequestProgressTrackerLogFilter
Date Mon, 03 Nov 2014 15:18:34 GMT

     [ https://issues.apache.org/jira/browse/SLING-4114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Bertrand Delacretaz updated SLING-4114:
---------------------------------------
    Summary: Compact and more specific logs from RequestProgressTrackerLogFilter   (was: Reduce
amount of log output from RequestProgressTrackerLogFilter )

> 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.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)

Mime
View raw message