> 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/devices/alerts-and-notifications/alerts.md).

# Alerts

Review urgent device and server alerts, then continue to the right follow-up action.

Review high-priority device and server alerts from the **Alerts** panel.

### When to use this page

Use this page when you need to investigate an urgent event quickly.

Use it to identify the affected device, confirm the alert type, and move into the next action.

### Before you start

Confirm that you know:

* whether you are looking for a recent urgent issue
* which device, hierarchy, or alert type may be affected
* whether the next step is investigation or alert configuration

### Alerts panel

The panel shows the top 50 high-priority alerts.

Select an alert to open the full **Alerts** screen and review its details.

<div data-with-frame="true"><figure><img src="https://content.gitbook.com/content/dzivQyj8aHN5Kvmx8apX/blobs/damjZnJIfQaqKcEiMDh9/image.png" alt=""><figcaption></figcaption></figure></div>

### Use alerts to

* identify urgent events quickly
* open the affected device or alert details
* continue to follow-up or configuration tasks

### Review the alert entry

When you open an alert, check these details first:

1. Confirm the alert type and severity.
2. Confirm the affected device or scope.
3. Decide whether the event needs device investigation or rule review.

### Choose the follow-up action

* **Device-specific event** — open the device record and review its current status and history.
* **Repeated or unexpected alert type** — review [Alert administration](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications/alert-administration).
* **Unclear estate-level pattern** — return to [Alerts and notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications).

Do not change alert configuration before confirming the alert is not a real operational issue.

### Verify the result

After you review the alert, confirm that:

* the alert matches the issue you expected
* the affected device or entity is clear
* you know whether to continue to device investigation or alert administration

### Result

You can identify urgent issues, confirm their scope, and choose the correct follow-up path.

### Next steps

* [Alerts and notifications](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications) — return to the alert center
* [Alert administration](https://verifone.gitbook.io/us-core-help-center/verifone-central/verifone-central/devices/alerts-and-notifications/alert-administration) — change subscriptions or alert rules


---

# 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/verifone-central-getting-started/verifone-central/verifone-central-device-manager/devices/alerts-and-notifications/alerts.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.