> 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/settings-for-each-wan-interface.md).
# Settings for each WAN interface
Configure Health Monitor tests for each WAN interface.
Configure the tests performed on each available WAN interface.
| Field | Description |
| ---------------------------- | ---------------------------------------------------------------------------------------- |
| Priority | Determines which interface is preferred when multiple WAN interfaces exist. |
| Interface | Name of the WAN interface being monitored. |
| Ping address | Address used for connectivity tests. Enter multiple addresses as a comma-separated list. |
| DNS lookup | Domain name resolved to check DNS operation. |
| Time between interface tests | Interval between tests for this interface. |
| Health monitoring | Enables or disables monitoring for this interface. |
Use **Promote** to increase an interface's priority. Use **Remove** only when an interface should no longer be monitored.
A new interface appears after you create its corresponding physical interface. Use values approved for the installation.
---
# 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.eseye.com/hera604/diagnostics-and-maintenance/health-monitor/settings-for-each-wan-interface.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.
