> For the complete documentation index, see [llms.txt](https://help.santesuite.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.santesuite.org/operations/cdr-administration/santedb-administration-panel/system-administration/probes.md).

# Probes

The probes screen shows a summary of all installed `IDiagnosticsProbe` implementations on the dCDR or iCDR to which the administration panel is connected. These probes provide a real-time reading of available operating system and internal system data.

![](/files/63gKKRqkrjVHVNNvUg77)

Probes are used to diagnose the overall health and status of the server. Any plugin can implement an `IDiagnosticsProbe` (see: [Documentation](http://santesuite.org/assets/doc/net/html/T_SanteDB_Core_Diagnostics_IDiagnosticsProbe_1.htm)) for any reading it wishes to emit to administrators. 

By default the probes on SanteDB are:

| Probe       | Description                                                                                                                                                                                                                                                              | Components                                                                                                                                                                                                                                                               |
| ----------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Thread Pool | SanteDB iCDR and dCDR use their own ThreadPool for asynchronous operations. This implementation allows cross-platform use of a consistent thread pool without consuming the underlying .NET thread pool.                                                                 | <p>Pool Size: The maximum number of concurrent actions allowed in the thread pool</p><p>Pool Use: The number of worker threads which are currently busy servicing requests</p><p>Queue Depth: The number of waiting tasks which are waiting for an available worker.</p> |
| Machine     | The machine probe shows underlying use statistics from the host environment on which the iCDR or dCDR is running. Currently these probes values are only available on Windows Operating Systems.                                                                         | <p>CPU Use: The % use of all CPUs on the iCDR or dCDR machine</p><p>Memory Use: The % use of system memory on the iCDR or dCDR machine</p><p>Disk Use: The % busy time of the disk infrastructure on the iCDR or dCDR machine</p><p></p>                                 |
| REST Pool   | The REST server pool probe is used for diagnosing issues on the REST based API. In SanteDB the REST APIs use their own thread pool (separate from the system thread pool), this thread pool use statistic shows the occupation of HTTP requests waiting to be processed. |                                                                                                                                                                                                                                                                          |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.santesuite.org/operations/cdr-administration/santedb-administration-panel/system-administration/probes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.