[
https://issues.apache.org/jira/browse/SLING-8786?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Krystian Nowak updated SLING-8786:
----------------------------------
Description: Thread pool metrics exposed via [Sling Commons
Metrics|https://github.com/apache/sling-org-apache-sling-commons-metrics] would
be helpful e.g. to identify thread pool exhaustion and being able to measure
e.g. ExecutorActiveCount (most likely as a
[gauge|https://sling.apache.org/apidocs/sling11/org/apache/sling/commons/metrics/Gauge.html])
(was: Thread pool metrics exposed via [Sling Commons
Metrics|https://github.com/apache/sling-org-apache-sling-commons-metrics] would
be helpful e.g. to identify thread pool exhaustion and being able to measure
e.g. ExecutorActiveCount)
> Expose thread pool metrics
> --------------------------
>
> Key: SLING-8786
> URL: https://issues.apache.org/jira/browse/SLING-8786
> Project: Sling
> Issue Type: Improvement
> Components: Commons
> Affects Versions: Commons Threads 3.2.18
> Reporter: Krystian Nowak
> Priority: Major
> Fix For: Commons Threads 3.2.20
>
> Attachments: SLING-8786.diff, ThreadPoolMetricsGauges.java
>
>
> Thread pool metrics exposed via [Sling Commons
> Metrics|https://github.com/apache/sling-org-apache-sling-commons-metrics]
> would be helpful e.g. to identify thread pool exhaustion and being able to
> measure e.g. ExecutorActiveCount (most likely as a
> [gauge|https://sling.apache.org/apidocs/sling11/org/apache/sling/commons/metrics/Gauge.html])
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
