How-tos Concepts Training paths

How to acknowledge open alerts

Wiki: Now concepts, Alerts

When to use this

You want to triage plant-wide alerts from one place, without hunting through each individual screen for the badge that triggered it, whether that’s a production exception (a KPI breach, andon call, or overdue PM) or a system health issue (a stale tag, a dark kiosk display, a platform problem), and you want the same one place to review what has already been handled.

Steps

  1. Click Alerts in the sidebar (/alerts), click “View all” on the notification bell’s dropdown, or click “See all alerts” on a node’s own Open alerts card (Node Detail’s Performance tab) to land here pre-scoped to that node.
  2. The list opens on Production alerts by default, the KPI rule breaches, andon calls, and preventive maintenance that need your attention right now. Switch the Alert type filter to System health for tag health, platform, and display alerts, or All alerts to see everything together.
  3. Narrow the list further with the rest of the filter bar: Severity, Source (KPI alert, preventive maintenance, tag health, andon call, platform health, kiosk display down, or gateway offline), Node (search-to-filter, rolls up across that node’s subtree), and free-text Search over each alert’s title and message.
  4. Review the open-alerts list. Each row shows severity, the alert’s title and message, and how long ago it fired. A condition that keeps re-firing (a threshold hovering right at the line, a display flickering on and off) doesn’t pile up as repeat rows: the same alert shows a × count and “last fired” time instead, so the list stays one row per real, distinct problem. Alerts feed
  5. Click Ack on a row you’ve handled. This calls POST /api/v1/alerts/{id}/ack and the alert updates/removes from the list immediately, no full page reload.
  6. To clear everything at once, click Ack all (admins only) and confirm. It acknowledges every open alert currently listed, honoring the Alert type toggle along with the other filters. It stands down when you’re viewing a node-filtered, source-filtered, or search-filtered list, so it never acknowledges more than what’s on screen.
  7. To review what has already been handled, switch Status from Open to Acknowledged (history). Each row shows who acknowledged it and when. Switch Status to All to see open and acknowledged alerts together.
  8. Below the alert list, a PLC alarms card summarizes machine alarm activations for the selected time range: activation counts, active time, and any tag that is chattering (firing faster than anyone could reasonably respond to). When every configured alarm tag has zero activations, the card collapses to one line, click it to see the full detail.

Notes

  • The list loads the 200 most recent matching alerts at a time. If there are more, a Show more button appears below the list, click it to load additional alerts.
  • Alerts start in an open status. Acknowledging is a one-way action from this screen (there’s no un-acknowledge here).
  • A re-firing alert bumps the count on its existing row instead of creating a new one, but every individual firing is still recorded behind the scenes, nothing about the history is lost, only the open list stays readable.
  • Which channel you personally get pinged through when a new alert fires is a separate setting, see How to configure notification preferences.