# Health Alerts

Health Alerts is the detail behind the Health Report grid. Every individual alert raised across the estate, with its device, category, description, severity, and acknowledgment state, plus the controls to work through them and push them into ServiceNow.

## What this screen shows

A single grid, one row per alert. Volume is high by nature: an estate of any size carries hundreds of open alerts at once, which is why the default view filters to unacknowledged only rather than showing everything ever raised.

| Column | What it holds |
| --- | --- |
| ID | Numeric alert identifier |
| Context | The domain the alert came from, for example Storage Device |
| Collection Date | When the alert was captured |
| Severity | Warning or Alert, shown as an icon |
| Device Name | The device that raised it |
| Display Name | The friendly name for that device |
| Category | The health category, matching the columns on Health Report |
| Alert | The alert type, for example a quota condition |
| Description | The detailed message |
| Acknowledged? | Current acknowledgment state |
| Service Now | Per-row integration control |

A `Count` column is available in the column chooser but hidden by default. Alert categories track the Health Report columns, with storage layout conditions such as hard and advisory quota issues making up the bulk of what most estates see.

## Filtering to the work that matters

- **Acknowledged.** `All`, `Yes`, or `No`. Defaults to `No`, so you land on open work rather than history.
- **Severity.** `All`, `Warning`, or `Alert`. Defaults to `All`.

Unacknowledged plus `Alert` is the shortest list on the screen and the one to read first. Everything else is a backlog. On top of the two dropdowns there is a search box for text matching across the grid, and a row-grouping zone, so grouping by category or device turns a flat list of hundreds into a handful of themes.

## Acknowledging alerts

Acknowledging hides an alert from the default view. Shift and click to select several rows, then acknowledge them together. The screen accepts up to ten rows per acknowledgment action, so large cleanups happen in batches rather than one at a time.

> **Important:** Acknowledged means handled, not fixed. The underlying condition is still on the device; you have only removed the alert from the working list. Acknowledge after you have resolved something or decided it is expected, not simply to shorten the list.

## ServiceNow integration

Each row carries a ServiceNow control that creates or links an incident ticket for that alert. Escalation therefore happens without anyone retyping the device, category, and description into a second system, and the ticket keeps its link back to the alert that raised it.

## The alert-handling workflow

1. Start on [Health Report](https://visualoneintelligence.com/docs/storage-health-report/) and find the devices showing warnings or critical status.
2. Come here and filter by severity to isolate the critical items.
3. Read the description and category for the context behind the indicator.
4. Raise a ServiceNow ticket for anything needing escalation.
5. Acknowledge once resolved, which returns the device to green on the Health Report.

## Related screens

[Health Report](https://visualoneintelligence.com/docs/storage-health-report/) is the summary this screen sits underneath. [Enterprise Summary](https://visualoneintelligence.com/docs/storage-enterprise-summary/) carries the alert counts that tell you whether the backlog is growing. [Delta Report](https://visualoneintelligence.com/docs/storage-delta-report/) helps establish whether a new alert coincides with a real change in the environment.

---

Source: https://visualoneintelligence.com/docs/storage-health-alerts/