> For the complete documentation index, see [llms.txt](https://docs.ostara.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ostara.dev/features/instance-features/jvm/thread-profiling.md).
# Thread Profiling
### Overview
Thread Profiling allows you to to profile the threads within your application for a set amount of time, after which you will be able to explore the results of the profiling.
### Usage
To initiate a new profiling, click the **Request Thread Profiling** at the top right
Upon completion, click the **View Details** action to reveal the profiling window
The profiler runs for 60 seconds and gathers all thread dumps form this time, grouping the data by thread and thread state over time.
\- Represents threads in a `RUNNING` state
\- Represents threads in a `WAITING` state
\- Represents threads in a `TIMED_WAITING` state
Each grouped block is expandable and will show the thread's details, as well as the stack trace. Multiple blocks can be expanded at a time.
### Required Abilities
* [Thread Dump](/features/abilities.md)
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.ostara.dev/features/instance-features/jvm/thread-profiling.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
