# Decision to throttle based on a condition **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [September 21, 2018, 4:25pm UTC](https://discuss.elastic.co/t/decision-to-throttle-based-on-a-condition/149489 "2018-09-21T16:25:16Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![gautu7](https://avatars.discourse-cdn.com/v4/letter/g/c89c15/32.png) [@gautu7](https://discuss.elastic.co/u/gautu7)\ **Post date:** [October 4, 2018, 7:04pm UTC](https://discuss.elastic.co/t/decision-to-throttle-based-on-a-condition/149489/3 "2018-10-04T19:04:44Z")
@elastock Thanks, and sorry for being late to the party. To your first question, yes, I have a monitoring cluster which houses metrics of 'n' clusters so I have a single watcher which alerts when any node within the 'n' cluster hit the threshold. I have 2 actions, a slack-notification which always triggers and a jira-action which should trigger only once per node per 24 hour interval. If I have 2 indexes (monitoring and custom index) to filter on to check if the current node which has met the threshold and this node exists in the custom index before I go ahead and insert into the custom index in the action block, I would not be able to trigger my slack notification. I want both these actions to be kind of independent of each other in the same watch. Is this something which can be done or I need to have 2 independent watches with 1 action each? --- _[View the full topic](https://discuss.elastic.co/t/decision-to-throttle-based-on-a-condition/149489)._