# Optimising Kibana Indicator Match alert

**URL:** <https://discuss.elastic.co/t/optimising-kibana-indicator-match-alert/295668>\
**Category:** Kibana\
**Created:** [January 28, 2022, 8:39am UTC](https://discuss.elastic.co/t/optimising-kibana-indicator-match-alert/295668 "2022-01-28T08:39:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pruttle](https://avatars.discourse-cdn.com/v4/letter/p/7ea924/32.png) [@pruttle](https://discuss.elastic.co/u/pruttle)\
**Post date:** [January 28, 2022, 8:39am UTC](https://discuss.elastic.co/t/optimising-kibana-indicator-match-alert/295668/1 "2022-01-28T08:39:31Z")

</div>

Hi  
I am trying to alert against a large set of indices covered by the Indicator Index Pattern. These indices go back 3 years so there is a lot of data. When activated the alerting rule requires a lot of system resources and so is not practical to use.  
Is there a guide to optimizing alerting?  
Can the processing be spread across nodes or does it just occur on a Kibana instance?  
Are there any tweaks that can help with querying against a large set of indicators?  
Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 25, 2022, 8:39am UTC](https://discuss.elastic.co/t/optimising-kibana-indicator-match-alert/295668/2 "2022-02-25T08:39:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.