# Enabled building block option on rule but still mamy tickets

**URL:** <https://discuss.elastic.co/t/enabled-building-block-option-on-rule-but-still-mamy-tickets/301387>\
**Category:** SIEM\
**Tags:** detection-rules\
**Created:** [April 2, 2022, 12:02pm UTC](https://discuss.elastic.co/t/enabled-building-block-option-on-rule-but-still-mamy-tickets/301387 "2022-04-02T12:02:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![realtech2338](https://avatars.discourse-cdn.com/v4/letter/r/76d3ee/32.png) [@realtech2338](https://discuss.elastic.co/u/realtech2338)\
**Post date:** [April 2, 2022, 12:02pm UTC](https://discuss.elastic.co/t/enabled-building-block-option-on-rule-but-still-mamy-tickets/301387/1 "2022-04-02T12:02:33Z")

</div>

The main pain for our analyst is noise. For instance we have brute force rules if it matches 100+ hits we need to get one ticket but we are getting 100 tickets generated on out ticketing tool zendesk. I have even enabled even building block inside rule.

Do i need to do any other settings in my rule. Please help.

---

<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:** [April 30, 2022, 12:03pm UTC](https://discuss.elastic.co/t/enabled-building-block-option-on-rule-but-still-mamy-tickets/301387/2 "2022-04-30T12:03:34Z")

</div>

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