> 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/open-alerts.md).

# Open Alerts

This section discusses the Open Alerts Widget and Alert notifications.

<details>

<summary>Keywords</summary>

Also called: Alerts widget, Alerts chart, alert severity levels. Search terms: open alerts, device missing alert, low battery alert, alert notifications.

</details>

## What is the Open Alerts chart?

Alerts notify of important events occurring in VHQ. You can specify the type of alerts sent and the method of notification (e-mail message or status screen). Some alerts are available only if specific modules such as *Diagnostics* or *Content Management* are implemented. In the VHQ Dashboard, hover over the graph in the **Alerts** widget to view the alert severity level (high, medium, and low).

The alerts can be generated by the terminal and logged to the server by the terminal agent based on configuration, such as the *Low Battery* alert generated by a device. They can also be generated by the VHQ server upon analyzing the data received from the terminal.

{% hint style="info" %}
When the VHQ server determines that an active device has not sent any heartbeat message for more than 24 hours, it raises the **Device Missing** alert for that device.
{% endhint %}

All alerts generated by the VHQ Agent on the device can be individually configured as **On/Off** based on the value of the alert mask specified in the VHQ Agent configuration file. Alerts have a severity level (high / medium / low), and severity levels can be configured from VHQ. **Only high-severity alerts spawn a visual notification in VHQ.** Email notification for all alert types can be configured on a per-user basis.

The **Alerts** widget displays information about alerts generated during the past seven days. If no alerts were generated in that period, the status message *No Alerts found* is displayed. This message also appears when VHQ is unable to retrieve chart data from the VHQ server.

<figure><img src="https://600591075-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHUGEtJbVPg5OkUtYCm8j%2Fuploads%2FJPpqbgtyPnBXoibCZDYA%2Fimage.png?alt=media&#x26;token=8b667f0d-0b79-4b29-8cda-ce2ef3239bf0" alt="Open Alerts widget"><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 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.verifone.com/support-us/verifone-hq/vhq-dashboard-overview/open-alerts.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.
