# Filter Alarm take long time and seems to be applied to all the data

**URL:** <https://forum.inductiveautomation.com/t/filter-alarm-take-long-time-and-seems-to-be-applied-to-all-the-data/107021>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [June 4, 2025, 2:17pm UTC](https://forum.inductiveautomation.com/t/filter-alarm-take-long-time-and-seems-to-be-applied-to-all-the-data/107021 "2025-06-04T14:17:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [June 4, 2025, 2:17pm UTC](https://forum.inductiveautomation.com/t/filter-alarm-take-long-time-and-seems-to-be-applied-to-all-the-data/107021/1 "2025-06-04T14:17:05Z")

</div>

**FilterAlarm extension Function for Persepctive Alarm Journal** component take somtimes long time...

```python
Alarm Journal Table at [0:2] took 1 minutes to process 2592 alarm query results. Avoid any blocking work in the 'filterAlarm' extension function, and consider using condition filters to reduce the number of query results.

```

It seems to be applied to all the data regardless the filter configured on component:  
**filter.condition.source / displayPath / provider**?

in my understanding, the component apply the filter with filter.condition.source / displayPath / provider (and priority filter...) and pass the data to extension Function FilterAlarm