# +1 for automatic acknowledgement in watcher **URL:** \ **Category:** Elasticsearch\ **Tags:** elastic-stack-alerting\ **Created:** [June 1, 2017, 12:14am UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824 "2017-06-01T00:14:16Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\ **Post date:** [June 1, 2017, 12:14am UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/1 "2017-06-01T00:14:16Z")
Hi, I see a couple questions from last year about the capability to automatically acknowledge a watch within the definition of a watch itself (including links to those questions below, for reference). Are there any updates on that as a feature? And/or, would it be possible to do it as a webhook action? > [@Generic watch, specific alerts, duplicate alerting?](https://discuss.elastic.co/t/generic-watch-specific-alerts-duplicate-alerting/51610): > > Imagine that I have 100 machines to monitor and that each machine is named by its number (i.e. the first machine is named ("1"). Imagine that I wish to alert if the disk usage is over 90% on any of the machines. Imagine that LogStash is inserting data into ES every minute with the current disk percentage for each machine. I would like to send an alert to pagerduty for every machine that is over 90% disk usage. I know how to craft my search query to find machines with disk usage over 90%. Su… > [@How can I get Automatic Acknowledgement-based Throttling?](https://discuss.elastic.co/t/how-can-i-get-automatic-acknowledgement-based-throttling/51489): > > This page: [https://www.elastic.co/guide/en/watcher/current/watch-acknowledgment-throttling.html](https://www.elastic.co/guide/en/watcher/current/watch-acknowledgment-throttling.html) suggests that an action will only be executed once (until the condition becomes false and then true again). I would like to get that behavior. However, I'm not clear on how I would achieve this "one alert per condition". I viewed this page: [https://www.elastic.co/guide/en/watcher/current/actions.html](https://www.elastic.co/guide/en/watcher/current/actions.html). When I read that page, I see that can manually "ack" an alert, but I want the alert to work aut… Thanks, Casie ---
**Author:** ![skearns](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skearns/32/125945_2.png) [@skearns](https://discuss.elastic.co/u/skearns)\ **Post date:** [June 1, 2017, 12:09pm UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/2 "2017-06-01T12:09:49Z")
Hi Cassie, Can you share a bit about your use-case and how you would use an auto-acknowledge feature vs. the existing throttling capabilities? Thanks, Steve ---
**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\ **Post date:** [June 1, 2017, 4:17pm UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/3 "2017-06-01T16:17:32Z")
We ingest incident data into a single incidents index. If a document with a priority 1 incident is created in the index, the document will keep it's priority 1 status and its "Open" status for an indefinite amount of time. We want to query this index for any P1/open incidents but only ever alert one time. Currently I have it set to query the index for any P1/open incidents created in the last twenty minutes, and I have a 30 minute throttle period defined, and that will work ok _except_ for if there is a delay in ingesting data. For example: a P1 incident is created at 10 AM today, but something in our ingestion pipeline fails, we don't ingest any data between 10-11AM, we get the data in there at 11:00. . .the watch looks for anything from within the last 20 minutes, and doesn't find any. Does that help? ---
**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\ **Post date:** [June 1, 2017, 5:15pm UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/4 "2017-06-01T17:15:10Z")
> [@casieowen](#): > > but something in our ingestion pipeline fails, we don't ingest any data between 10-11AM, we get the data in there at 11:00. . .the A couple other things I'm thinking might work: 1. Can a watch modify data in the index itself? So, if we added a field for "alerted", could the watch populate that field? 2. We're currently indexing the payload of the watch query into a watch\_p1 index. I'm going to see if I can define the watch query to look for an open, P1 incident for which there is no document in the watch\_p1 index (since that would only get created by a watch execution that would have already alerted). Let me know if you have any other thoughts and/or what plans are re: auto acknowledgement for watches. Thanks! Casie ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [June 1, 2017, 9:30pm UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/5 "2017-06-01T21:30:56Z")
This is definitely something you should also ask your Elastic support engineer 🙂 ---
**Author:** ![casieowen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/casieowen/32/8734_2.png) [@casieowen](https://discuss.elastic.co/u/casieowen)\ **Post date:** [June 2, 2017, 12:29am UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/6 "2017-06-02T00:29:17Z")
Yeah, I was thinking of doing that, but since I saw other people asking for this feature here in the community. . . But, yes, Mike, here I come. Mike is awesome all the time, so that helps. Casie ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 30, 2017, 12:29am UTC](https://discuss.elastic.co/t/1-for-automatic-acknowledgement-in-watcher/87824/7 "2017-06-30T00:29:25Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.