> For the complete documentation index, see [llms.txt](https://hashman.gitbook.io/hashman-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hashman.gitbook.io/hashman-docs/features/miners.md).

# Miners

<figure><img src="/files/lYtsjpZJCmriGhzFa8hF" alt=""><figcaption><p>Miners view</p></figcaption></figure>

### Key features

#### Location management

* Hierarchical view of mining sites
* Quick filtering by location
* Organized fleet overview

#### Miner list

* Real-time status dashboard
* Customizable data columns
* Key metrics at a glance:
  * 24h hashrate
  * Power mode
  * Temperature
  * Network status
  * Mining profile

#### Health monitoring

* Instant alerts for critical issues
* Proactive failure detection
* Automatic health checks for:
  * Hashboards
  * Fans
  * Network connectivity
  * Temperature thresholds

#### Fleet operations

* Bulk actions across miners
* Scheduled maintenance windows
* Automated task management
* Remote firmware updates
* Power mode optimization

#### Detailed analytics for single miners

* Per-miner performance graphs
* Historical data tracking
* Secure remote access
* Custom scheduling options
* Comprehensive logs


---

# 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://hashman.gitbook.io/hashman-docs/features/miners.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.
