[
https://issues.apache.org/jira/browse/OAK-10054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Mueller resolved OAK-10054.
----------------------------------
Assignee: Thomas Mueller
Resolution: Fixed
> Improved trace level logging of JCR method calls
> ------------------------------------------------
>
> Key: OAK-10054
> URL: https://issues.apache.org/jira/browse/OAK-10054
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Reporter: Thomas Mueller
> Assignee: Thomas Mueller
> Priority: Major
> Fix For: 1.48.0
>
> Attachments: OAK-10054.patch
>
>
> To analyze calls to the JCR API we can enable trace level logging. However,
> currently only the operation is logged (e.g. getNode), but not the path.
> Also, applications that have thousands of JCR method calls will write too
> many log messages.
> That means we currently have both too much logging (too many lines), and not
> enough logging (not logging useful info).
> It would be good if with trace level setting enabled, JCR method calls are
> logged in more detail (e.g. path), and optionally with sampling.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
