You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Davide Giannella (JIRA)" <ji...@apache.org> on 2016/03/10 12:20:41 UTC
[jira] [Closed] (OAK-4010) Log major operation done in Oak via
specific operation logger
[ https://issues.apache.org/jira/browse/OAK-4010?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Davide Giannella closed OAK-4010.
---------------------------------
Bulk close for 1.4.0
> Log major operation done in Oak via specific operation logger
> -------------------------------------------------------------
>
> Key: OAK-4010
> URL: https://issues.apache.org/jira/browse/OAK-4010
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: core
> Reporter: Chetan Mehrotra
> Assignee: Chetan Mehrotra
> Priority: Minor
> Fix For: 1.4, 1.4.0
>
>
> Currently we use dedicated logger for recording writes and reads (OAK-2011). We should do similar logger in some other parts of Oak
> # Query - At jcr.query.QueryManagerImpl#executeQuery where we send the stats. Just log query with timing
> # BlobStoreStats - Upload and download of blobs
> This would be useful when used with new Sling Tracer support for recording (SLING-5507, SLING-5459) and would allow one to determine what major operations are done in given HTTP request along the whole Oak layer (query, writes, blob uploaded, query fired to Mongo) etc
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)