You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Joerg Hoh (Jira)" <ji...@apache.org> on 2021/11/28 14:41:00 UTC

[jira] [Created] (SLING-10945) Add metrics to Sling ResourceResolver

Joerg Hoh created SLING-10945:
---------------------------------

             Summary: Add metrics to Sling ResourceResolver
                 Key: SLING-10945
                 URL: https://issues.apache.org/jira/browse/SLING-10945
             Project: Sling
          Issue Type: Improvement
          Components: ResourceResolver
            Reporter: Joerg Hoh


Currently the Sling ResourceResolver (bundle) does not expose any metrics, but from an operational point of view it would be good if at least some basic metrics could get exposed.

I would like to start with

# number of VanityPaths
# number of aliases
# number of unclosed ResourceResolvers

1 + 2 are important to determine if the instance might be affected by the limits of JCR queries, while the third can help to understand quickly if a memory issue can be caused by leaking ResourceResolvers (with potentially embedded JCR sessions).

This requires to add a dependency to the Sling Metrics bundle.





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