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 "Thomas Mueller (Jira)" <ji...@apache.org> on 2021/11/17 11:02:00 UTC

[jira] [Created] (OAK-9624) Queries: Add logging to determine the caller

Thomas Mueller created OAK-9624:
-----------------------------------

             Summary: Queries: Add logging to determine the caller
                 Key: OAK-9624
                 URL: https://issues.apache.org/jira/browse/OAK-9624
             Project: Jackrabbit Oak
          Issue Type: Documentation
          Components: query
            Reporter: Thomas Mueller


It's often helpful to know the caller (module) of a query:
* queries that read many nodes
* queries that exceed the limits
* queries that are slow
* queries that don't use an index
* query statistics

Some configuration is needed, e.g. which packages to ignore. A simple way would be to create the stack trace, and iterate over the elements. It would be a bit slow if done for each query however - e.g. we shouldn't probably do it for very fast internal queries (like, oak-internal queries).



--
This message was sent by Atlassian Jira
(v8.20.1#820001)