> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/details.md).

# Details

The Details page gives graphic details for each watch. There are different types of details pages for bearer, switches, and Wireless Access Points (WAPs). A bearer page will have additional sections if performance tests or traffic analysis (NBAR or Flow) has been enabled.

### Details page header

* [**Details page header** For all watch types, options available, watch title, time zone and time bar settings](https://help.highlight.net/details/details-page-options/header.md)

### Details pages

* [**Traffic Load** Total volume out and in, plus average and min/max traffic for the period displayed](https://help.highlight.net/details/details-pages/traffic-load.md)
* [**Broadband** Chart bandwidth speeds for a broadband line to indicate any issues](https://help.highlight.net/details/details-pages/broadband-bandwidth.md)
* [**Cellular Clarity** Chart the signal strength of a cellular connection against a custom threshold](https://help.highlight.net/details/details-pages/cellular-clarity.md)
* [**Line Availability** Key indicator of the status of a watch, showing impacting, non-impacting and excluded availability events](https://help.highlight.net/details/details-pages/line-availability.md)
* [**Performance** Results of performance tests displayed in visually powerful, easy to interpret charts](https://help.highlight.net/details/details-pages/performance-charts.md)
* [**Maintenance** Markers seen when a watch is in maintenance](https://help.highlight.net/details/details-page-options/maintenance-indicators.md)

### Bearers - Traffic Analysis

* [**NBAR and Flow** Feature comparison of NBAR and Flow for application data](https://help.highlight.net/details/bearers-traffic-analysis/nbar-and-flow.md)
* [**Flow specifics** Visibility of applications showing top sources and destinations, plus top conversations for each](https://help.highlight.net/details/bearers-traffic-analysis/flow-specifics.md)

### WiFi

* [**AP Access Point** Wireless Access Point - Access Point chart](https://help.highlight.net/details/wifi/ap-access-point.md)
* [**AP Client Count** Wireless Access Point - Client Count](https://help.highlight.net/details/wifi/ap-client-count.md)
* [**AP Channel Load** Wireless Access Point - Channel Load](https://help.highlight.net/details/wifi/ap-channel-load.md)
* [**WiFi by vendor** WiFi options available in Highlight in terms of vendors and features](https://help.highlight.net/details/wifi/wifi-by-vendors.md)

### Other watch types

* [**SD-WAN tunnels** See if tunnels are up, down or discontinued](https://help.highlight.net/details/other-watch-types/sd-wan-tunnels.md)
* [**Performance Agent** Check availability on performance agents and see associated performance tests](https://help.highlight.net/details/other-watch-types/performance-agent.md)
* [**Switches** Traffic levels, health issues and outages on every switch port displayed, 'critical' ports explained](https://help.highlight.net/details/other-watch-types/switches.md)
* [**Cameras and Sensors**  See availability and health blips](broken://pages/lljJrEaOdTgdfW38k1fl)


---

# 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://help.highlight.net/details.md?ask=<question>&goal=<user_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.
