# Alarm Metrics in provider level and reading it in script

**URL:** <https://forum.inductiveautomation.com/t/alarm-metrics-in-provider-level-and-reading-it-in-script/114441>\
**Category:** Ignition\
**Tags:** ignition83, scripting, perspective\
**Created:** [March 11, 2026, 1:08pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-in-provider-level-and-reading-it-in-script/114441 "2026-03-11T13:08:12Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![avaughn](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/avaughn/32/38972_2.png) [@avaughn](https://forum.inductiveautomation.com/u/avaughn)\
**Post date:** [March 17, 2026, 6:23pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-in-provider-level-and-reading-it-in-script/114441/9 "2026-03-17T18:23:20Z")

</div>

It looks like you’re running into a bug that will be fixed in 8.3.5. Currently available in the Nightly.

### Alarm Status

**[IGN-15336: Alarm metrics in nested folders sometimes incorrectly reflect active alarms](https://forum.inductiveautomation.com/t/nightly-8-3-changelogs-2026-and-beyond/113010/39)**  
Fixed an issue where Alarm Metrics in nested folders would initialize to empty and never update.

---

_[View the full topic](https://forum.inductiveautomation.com/t/alarm-metrics-in-provider-level-and-reading-it-in-script/114441)._