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 2022/01/19 13:57:00 UTC

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

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

Joerg Hoh closed SLING-10945.
-----------------------------

> Add metrics to Sling ResourceResolver
> -------------------------------------
>
>                 Key: SLING-10945
>                 URL: https://issues.apache.org/jira/browse/SLING-10945
>             Project: Sling
>          Issue Type: Improvement
>          Components: ResourceResolver
>    Affects Versions: Resource Resolver 1.7.10
>            Reporter: Joerg Hoh
>            Assignee: Joerg Hoh
>            Priority: Major
>             Fix For: Resource Resolver 1.8.2
>
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> 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)