open-telemetry / open-telemetry/opentelemetry-java-instrumentation
Add metrics for virtual thread
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 2.6k
- Forks
- 1.2k
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
I want to monitor the virtual thread and platform thread seperately
Describe the solution you'd like
We may add metrics for virtual thread or add label to seperate different kind of thread
Now we have JVM_THREAD_DAEMON and JVM_THREAD_STATE, is it possible to add a new label JVM_THREAD_TYPE or "is_virtual"?
Describe alternatives you've considered
No response
Additional context
No response
Tip
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing JVM_THREAD_DAEMON and JVM_THREAD_STATE metrics and reading how thread attributes are exposed. Clarify whether the intended result is a new metric or a JVM_THREAD_TYPE/is_virtual label, then define how virtual and platform threads should be distinguished and what separate monitoring output counts as done.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- observability-sre
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100