> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/verifone-hq/vhq-dashboard-overview/reporting-devices-chart.md).

# Reporting Devices Chart

This section discusses the Reporting Devices Chart Widget and its functions.

<details>

<summary>Keywords</summary>

Also called: Reporting Devices widget, heartbeat chart. Search terms: reporting devices, heartbeat message, device missing alert.

</details>

## What is the Reporting Devices chart?

The **Reporting Devices** chart, from the VHQ Dashboard, displays information about devices that have communicated with the VHQ server during the past seven days by sending heartbeat messages. If a device fails to communicate with the VHQ server during the past seven days, the status message *No Devices found* is displayed.

The *No Devices found* status message is displayed when VHQ is unable to fetch data from the VHQ server.

Hover over any section of a bar in the chart to display the number of devices reported to the VHQ server.

Multiple heartbeat messages sent by a device in a given day are counted as one device in the chart for that day.

The frequency at which the VHQ Agent sends heartbeat messages is configured in the VHQ Agent. If the VHQ Agent on a device fails to send at least one heartbeat message in a 24-hour period, the VHQ server generates a *Device Missing* alert for that device.

<figure><img src="https://600591075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHUGEtJbVPg5OkUtYCm8j%2Fuploads%2FLOpVCCk2xGHVNQJSZaEz%2Fimage.png?alt=media&#x26;token=0940e794-ab48-483d-8155-afadb8af49aa" alt="Reporting Devices chart"><figcaption></figcaption></figure>


---

# 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.verifone.com/support-us/verifone-hq/vhq-dashboard-overview/reporting-devices-chart.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.