Similar to system.alarm.queryJournal function. Using the alarm status data with a custom table, it would be greatly improve performance of the query if this data could be limited to a given time range.

Using the 'EventTime' key in any|all_properties keyword arg is useless because you cannot do a > or < comparison, only ' or !=. In some cases, it would be good to be able to include ALL active alarms, but only cleared alarms from within a given time range.