> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/hera604/diagnostics-and-maintenance/health-monitor/general-settings.md).
# General settings
Configure system-wide monitoring and recovery behaviour.
Configure system-wide monitoring and recovery behaviour.
### Global settings
| Field | Description |
| -------------------------------------- | ------------------------------------------------------------- |
| Interface prioritisation | Allows Health Monitor to change WAN route priority. |
| Metric shift | Amount applied to route metrics after a priority change. |
| Time between system polls | Interval between global Health Monitor checks. |
| Restart WAN interfaces | Restarts interfaces after the configured failed system polls. |
| Reboot router | Reboots the router after the configured failed system polls. |
| Method for choosing best WAN interface | Selects an interface using priority, response time, or both. |
Confirm recovery thresholds with the deployment owner before enabling automatic router reboots.
### Actions for failed interface tests
Configure these recovery actions for repeated interface-test failures:
* Restart the interface.
* Restart a mobile interface with another profile.
* Reset the interface.
Set a consecutive-failure threshold for each enabled action.
### Actions for zero-packet interface tests
These settings apply when an interface reports no packets across consecutive tests. Configure restart, profile change, or reset actions only when required.
### Ping and DNS requests
| Field | Description |
| -------------------------------- | ---------------------------------------------------------- |
| Ping timeout | Time to wait for a ping response. |
| Number unanswered before failure | Consecutive unanswered ping requests before a failed test. |
| DNS timeout | Time to wait for a DNS response. |
| Number unanswered before failure | Consecutive unanswered DNS requests before a failed test. |
A single unanswered request does not necessarily indicate a failed connection.
---
# 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://docs.eseye.com/hera604/diagnostics-and-maintenance/health-monitor/general-settings.md?ask=&goal=
```
`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.
