# \[FEATURE\] Summarise Alarms in single rows in Alarm Journal Table (Vision & Perspective)

**URL:** <https://forum.inductiveautomation.com/t/feature-summarise-alarms-in-single-rows-in-alarm-journal-table-vision-perspective/49798>\
**Category:** Ignition\
**Tags:** vision, perspective\
**Created:** [August 11, 2021, 7:13am UTC](https://forum.inductiveautomation.com/t/feature-summarise-alarms-in-single-rows-in-alarm-journal-table-vision-perspective/49798 "2021-08-11T07:13:35Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [August 11, 2021, 7:13am UTC](https://forum.inductiveautomation.com/t/feature-summarise-alarms-in-single-rows-in-alarm-journal-table-vision-perspective/49798/1 "2021-08-11T07:13:35Z")

</div>

At the moment, looking at a history of alarms is difficult to piece together when all the events associated with an alarm occur as all of these are reported on individual rows (e.g. for active, acked, cleared).

It would be far simpler if unique alarm events only displayed on a single row, with the associated events simply adding to the same row in different columns (e.g. Ack Time, Cleared Time). What would also be good is to show the time to ack and time to clear as the time it took from first activation to be ackd/cleared.

Idea:

> **[Alarm Journal Table (Vision & Perspective) | Voters | Inductive Automation](https://inductiveautomation.canny.io/ignition-features-and-ideas/p/alarm-journal-table-vision-perspective)**

---

<div class="post-metadata">

**Author:** ![Ryan\_Allen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_allen/32/47013_2.png) [@Ryan\_Allen](https://forum.inductiveautomation.com/u/Ryan_Allen)\
**Post date:** [July 15, 2025, 9:25pm UTC](https://forum.inductiveautomation.com/t/feature-summarise-alarms-in-single-rows-in-alarm-journal-table-vision-perspective/49798/2 "2025-07-15T21:25:51Z")

</div>

Is this a thing yet? I've been banging my head against the wall seeing if this was possible using columnsAssociated or attempting to use the Alarm Status Table to display historical alarms.

---

<div class="post-metadata">

**Author:** ![gregory.sachs](https://avatars.discourse-cdn.com/v4/letter/g/e47774/32.png) [@gregory.sachs](https://forum.inductiveautomation.com/u/gregory.sachs)\
**Post date:** [July 16, 2025, 2:12pm UTC](https://forum.inductiveautomation.com/t/feature-summarise-alarms-in-single-rows-in-alarm-journal-table-vision-perspective/49798/3 "2025-07-16T14:12:40Z")

</div>

You can do a view or a query, something like this:

````python
CREATE VIEW [dbo].[vwAlarmDurationEndTime]
AS
SELECT TOP (100) PERCENT
	a.displaypath, SUM(DATEDIFF(SECOND, a.eventtime, COALESCE (c.eventtime, CURRENT_TIMESTAMP))) AS duration_sec, a.eventtime, a.priority, a.source, DATEADD(ss, DATEDIFF(SECOND, a.eventtime, COALESCE (c.eventtime, 
                  CURRENT_TIMESTAMP)), a.eventtime) AS EndDate
FROM dbo.alarm_events AS a 
                 LEFT OUTER JOIN
                  dbo.alarm_events AS c ON c.eventid = a.eventid AND c.eventtype = 1
WHERE (a.eventtype = 0) AND (((DATEPART(DW, a.eventtime) + @@DATEFIRST) % 7) NOT IN (0, 1))

GROUP BY a.displaypath, a.eventtime, a.priority, a.source, LEFT(a.displaypath, 8), DATEADD(ss, DATEDIFF(SECOND, a.eventtime, COALESCE (c.eventtime, CURRENT_TIMESTAMP)), a.eventtime)

ORDER BY duration_sec DESC, a.displaypath```
````