Read an alert
Open an alert, review its details, and set its status
An alert records a detected condition on a device or site.
This page covers reading and acting on existing alerts. Configuring monitors that generate new alerts is a separate task.
Open an alert from the map#
Open Explore. The overview panel lists Alerts at the top whenever the workspace is displaying them.
That list contains open alerts from the last 30 days, sorted by severity and then by recency, and it shows the first five. View all opens the full Alerts page.
Clicking a row opens the alert in the panel without leaving the map. From there you can open the device or site, which recenters the map and adds to the panel stack so you can step back through it.
Sites and devices with an open alert are tinted on the map, so a cluster of problems is visible before you open the list.
The map lists only open alerts from the last 30 days; acknowledged, ignored, and resolved alerts are on the Alerts page. If open alerts are missing as well, check Settings → Alerts: visibility may be turned off entirely, or the minimum severity may be raised — setting Critical suppresses Warning and Info alerts; setting Warning suppresses only Info alerts. Texture continues to capture suppressed alerts in the background.
Open an alert from the Alerts list#
Open Alerts in the left navigation. The table defaults to Open, and you can narrow it with Critical only or select one or more status chips — Open, Acknowledged, Ignored, Resolved — or switch to All. Multiple status chips can be active at once.
Clicking a row opens the alert drawer. The columns are severity, title, device, status, and time.
If you arrived from a site or device page, the list may already be filtered to that record. Open alerts also appear as banners at the top of a site or device page, and clicking a banner opens the alert drawer.
Read the alert details#
| Field | What it tells you |
|---|---|
| Severity | Critical, Warning, or Info, indicating how urgently the alert should be treated. |
| Status | Open, Acknowledged, Ignored, or Resolved. |
| Title and description | What fired, in the wording Texture mapped from the source system. |
| Timing | When the alert was created, along with acknowledged, ignored, or resolved timestamps and the user responsible, where those apply. |
| Device / Site | Where the alert occurred. View Device and View Site open the record, staying in the panel within Explore and opening the record's own page elsewhere. |
| Technical details | Type, subtype, provider, and source system, which help when the title is vague and you need to match an OEM message. |
Not every alert has a device, since some are raised against a site only.
Change the alert status#
An open alert offers three actions.
| Action | When to use it |
|---|---|
| Acknowledge | Someone is working the alert. It leaves the open list so that it is not worked twice. |
| Ignore | The alert does not represent a real issue, such as noise, an expected condition, or a duplicate. |
| Resolve | The condition has been addressed. You can also resolve an alert that is acknowledged or ignored. |
A resolved alert offers no further actions in the drawer. Status changes are shared, so everyone in the workspace sees the new state.
Investigate the underlying asset#
An alert names a device or site rather than a grid element. After opening the record, use Look up a member or site and Find and inspect an asset to examine the meter, the site, and the grid elements above it. If a chart or map pin looks empty, check Troubleshoot missing data before treating the alert as an outage.