# "Cooldown" for watches

**URL:** https://discuss.elastic.co/t/cooldown-for-watches/178937
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [April 29, 2019, 1:15pm UTC](https://discuss.elastic.co/t/cooldown-for-watches/178937 "2019-04-29T13:15:59Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![6tUBp3gwd9Zp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/6tubp3gwd9zp/32/45240_2.png) [@6tUBp3gwd9Zp](https://discuss.elastic.co/u/6tUBp3gwd9Zp)
#### Post date: [April 30, 2019, 12:18pm UTC](https://discuss.elastic.co/t/cooldown-for-watches/178937/3 "2019-04-30T12:18:52Z")

</div>

I already thought about that but the problem ist that if the value reaches the threshold a second time within the throttled time you wont get alerted. Considering this my best guess would be that you query the "trigger\_event.triggered\_time" from the ".watcher-history-\*" index in a chained input in your watcher and make your query-range of that watcher depending on that time-value.  
(It would be an approach little bit similar to: [https://discuss.elastic.co/t/watcher-alerting-time-issues-with-frequent-watch/68710/3?u=6tubp3gwd9zp](https://discuss.elastic.co/t/watcher-alerting-time-issues-with-frequent-watch/68710/3))  
Would that be even possible? If so how?

---

_[View the full topic](https://discuss.elastic.co/t/cooldown-for-watches/178937)._