jenkinsci / jenkinsci/support-core-plugin
[JENKINS-24850] Collect hot threads
- Dominant language
- Java
- Stars
- 19
- Forks
- 77
- Avg merge
- 17h 53m
- Merged PRs (30d)
- 3
Description
Collect thread dumps from the "hottest" threads, perhaps every n minutes.
Background:
https://weblogs.java.net/blog/brucechapman/archive/2008/03/hot_threads.html
http://java.dzone.com/news/porting-hot-thread-detector-vi
Example implementation: https://github.com/elasticsearch/elasticsearch/blob/1816951b6b0320e7a011436c7c7519ec2bfabc6e/src/main/java/org/elasticsearch/monitor/jvm/HotThreads.java
Sample output: https://gist.github.com/mlamp/3852210
---
Originally reported by
recampbell, imported from: Collect hot threads
schristou
Raw content of original issue
Collect thread dumps from the "hottest" threads, perhaps every n minutes.
Background:
https://weblogs.java.net/blog/brucechapman/archive/2008/03/hot_threads.html
http://java.dzone.com/news/porting-hot-thread-detector-viExample implementation: https://github.com/elasticsearch/elasticsearch/blob/1816951b6b0320e7a011436c7c7519ec2bfabc6e/src/main/java/org/elasticsearch/monitor/jvm/HotThreads.java
Sample output: https://gist.github.com/mlamp/3852210
Contributor guide
Research direction
Start by reading the linked hot-thread background and Elasticsearch HotThreads implementation, then compare the sample output. Define the collection interval and the expected hottest-thread dump format before identifying the plugin entry point; done means the support data includes periodic dumps for the hottest threads.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100