# Watcher Alerting on multi-bucket anomaly? **URL:** \ **Category:** Kibana\ **Tags:** elastic-stack-machine-learning, elastic-stack-alerting\ **Created:** [November 27, 2020, 7:46pm UTC](https://discuss.elastic.co/t/watcher-alerting-on-multi-bucket-anomaly/256911 "2020-11-27T19:46:46Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![richcollier](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/richcollier/32/115035_2.png) [@richcollier](https://discuss.elastic.co/u/richcollier)\ **Post date:** [November 30, 2020, 12:11pm UTC](https://discuss.elastic.co/t/watcher-alerting-on-multi-bucket-anomaly/256911/2 "2020-11-30T12:11:52Z")
See example here: > [@ML watcher configs](https://discuss.elastic.co/t/ml-watcher-configs/251696/3): > > Hi @richcollier, thank you for your reply. I have increased the interval and it looks working for missed results. however I found another inconsistency in the results which I'm not sure if related to interval or not - I had another watcher looking at a ML job results with a 10min bucket span and query\_delay around 15min. Watcher has a timestamp filter with the following config to be sure all the results are written and final. I noticed that a execution of watcher has fired for a record with a r… The field that defines if the anomaly is multi-bucket is: `multi_bucket_impact`. Anomalies with a `multi_bucket_impact` value of greater than or equal to 2 are considered multi-bucket impact anomalies and are marked with crosses in our UI. For more info see: [Interpreting multi-bucket impact anomalies using Elastic machine learning features | Elastic Blog](https://www.elastic.co/blog/interpreting-multi-bucket-impact-anomalies-using-elastic-machine-learning-features) --- _[View the full topic](https://discuss.elastic.co/t/watcher-alerting-on-multi-bucket-anomaly/256911)._