# \[FEATURE\] Alarm Metrics - Add overall "Status" integer

**URL:** <https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296>\
**Category:** Ignition\
**Created:** [November 20, 2025, 6:48am UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296 "2025-11-20T06:48:03Z")\
**Posts on this page:** 5\
**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:** [November 20, 2025, 6:48am UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296/1 "2025-11-20T06:48:03Z")

</div>

In the diy version I was using in previous versions, I had a single “Status” integer tag that summarised all alarm states in the folder, e.g.

```python
if({[.]Active Unack}, 1, // Alarms active and unacked
if({[.]Active Ack}, 2, // ALarms active but all ackd
if({[.]Clear Unack}, -1, // Alarms all cleared but unacked
0))) // No alarms active or unackd

```

I used this in the display bindings for alarm symbols/colour to make them:

- flash (unacked alarms exist; Status = 1)
- solid (all alarms acked but still active; Status = 2), and
- **to display it at all (Status \> 0)**

I also had a tag with the highest priority as an integer (in the Alarm Metrics there’s only a string version) so that I could more easily find the min/max from a list of priority values. E.g. if you want to know the max/min priority for a range of folders.

---

<div class="post-metadata">

**Author:** ![Nol](https://avatars.discourse-cdn.com/v4/letter/n/8e8cbc/32.png) [@Nol](https://forum.inductiveautomation.com/u/Nol)\
**Post date:** [November 20, 2025, 5:27pm UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296/2 "2025-11-20T17:27:28Z")

</div>

It’s a handy way to go for sure. One small suggestion but I find case statements to be nicer looking in this instance with less brackets to fuss about if you add more states.

```python
case(true,
	{[.]Active Unack},1,
	{[.]Active Ack}, 2,
	{Clear Unack}, -1,
	0
)

```

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [December 29, 2025, 4:33pm UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296/3 "2025-12-29T16:33:57Z")

</div>

I'd love to see a Bool hasActiveUnack added as well.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [December 29, 2025, 11:08pm UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296/4 "2025-12-29T23:08:46Z")

</div>

I believe you can use wildcard notation on the priority. From [Ignition 8.3 - Runtime Alarm Metrics](https://www.docs.inductiveautomation.com/docs/8.3/platform/tags/tag-properties/tag-alarm-properties#runtime-alarm-metrics-properties):  
`HasActiveUnacked(*)`

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [December 30, 2025, 1:36pm UTC](https://forum.inductiveautomation.com/t/feature-alarm-metrics-add-overall-status-integer/112296/5 "2025-12-30T13:36:34Z")

</div>

Ahh.. I'll have to give it a shot.