Appearance
Alarm Table
A live table of active alarms, or a historical alarm journal.
In Studio
In Studio, double-click Alarm Table in the Components category of the Components panel. It is added to the open view, where you can drag it into place.
When to use
Use Alarm Table on an overview or alarm-summary screen. Set Show Journal to review acknowledged/historical alarm activity rather than the current active list.
Properties
| Property | Type | Default | Description |
|---|---|---|---|
| Title | String | Active Alarms | The header text. Defaults to "Active Alarms" or "Journal" depending on Show Journal when left blank. |
| Show Journal | false, true | false | False (default) shows currently active alarms, with an Ack action per row. True shows the alarm journal (historical events) instead, with no Ack column. |
| Filter State | all, unacknowledged, acknowledged | all | Restricts the active-alarm list to all, unacknowledged, or acknowledged rows. Has no effect when Show Journal is true. |
| Max Rows | Number | 100 | The maximum number of rows fetched and shown. |
| Refresh (s) | Number | 10 | The polling interval in seconds, used only as a fallback while the table's live WebSocket feed is not connected — once connected, updates arrive immediately and polling drops to a slow 60-second background check. The fallback polling rate is clamped to at most every 10 seconds regardless of what is entered. |
| Source Filter | String | (none) | A tag folder. Only alarms whose source tag is that folder or under it are shown, e.g. one device's alarms on its popup. Accepts {view.params.X} and {page.params.X}. Blank = no filter; set but empty or unresolved shows no rows. |
| Show Ack All | false, true | false | True adds an Ack All button that acknowledges every alarm the table is showing (after its filters). |
Binding
This component has no single value binding.
No value binding — the table fetches its own data from the alarm API and a live WebSocket feed. Acknowledging a row (when Show Journal is false) posts an acknowledgement, which counts as a write action on the underlying alarm, not a tag write.