[
https://issues.apache.org/jira/browse/SLING-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15937812#comment-15937812
]
Georg Henzler commented on SLING-6698:
--------------------------------------
Example screenshots: [^threads-hc-idle.png] [^threads-hc-warn.png]
> Thread Usage Health Check
> -------------------------
>
> Key: SLING-6698
> URL: https://issues.apache.org/jira/browse/SLING-6698
> Project: Sling
> Issue Type: New Feature
> Components: Health Check
> Reporter: Georg Henzler
> Assignee: Georg Henzler
> Attachments: threads-hc-idle.png, threads-hc-warn.png
>
>
> This health check should use java.lang.management.ThreadMXBean to provide the
> following:
> * A quick overview what an instance is doing via http (there are many other
> means of monitoring, but there is nothing easier than using the the HC
> servlet). This works well as all relevant tasks in sling (requests, jobs,
> schedulers) set the thread name to a meaningful name
> * It should WARN if all threads are highly utilised (but never send CRITICAL
> as a fully utilised instance is not necessarily a problem)
> * It should use the deadlock detection of ThreadMXBean of send CRITICAL
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
