Getting a summary of alarms requires computationally expensive polled system.alarm.queryStatus() functions or isAlarmActiveFiltered() expressions.
It is commonly required to have this summary available for summary display purposes, such as any alarm present on a UDT or any alarm in an area (under a starting tag path).
Providing an automatically updated count on a folder level, similar to what is available per tag where alarms are configured, will solve this problem