# ML watcher configs

**URL:** <https://discuss.elastic.co/t/ml-watcher-configs/251696>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-machine-learning\
**Created:** [October 11, 2020, 11:51pm UTC](https://discuss.elastic.co/t/ml-watcher-configs/251696 "2020-10-11T23:51:15Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![saraKM](https://avatars.discourse-cdn.com/v4/letter/s/ecccb3/32.png) [@saraKM](https://discuss.elastic.co/u/saraKM)\
**Post date:** [October 26, 2020, 12:07am UTC](https://discuss.elastic.co/t/ml-watcher-configs/251696/3 "2020-10-26T00:07:42Z")

</div>

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 record\_score of 85 which I couldn't find in ml-anomalies results. However I found a record with the same values (timestamp, typical, actual, ..) and a record\_score=24 and initial\_record\_score=85. So it looks that the score has been updated after bucket results have been finalized (is\_interim:false). Is that an expected behavior? I was expecting that the score normalization happen before is\_interim:false are written.

```auto
           "filter": {
                "range": {
                  "timestamp": {
                    "gte": "now-3h/h",
                    "lt": "now-1h/h"
                  }}},
              "must": [ {
                  "terms": {
                    "result_type": [
                      "record"
                    ] } },
                {
                  "range": {
                    "record_score": {
                      "gt": 75}}},
                {
                  "range": {
                    "multi_bucket_impact": {
                      "lt": 2}}},
                {
                  "match": {
                    "is_interim": false}}
              ]

```

---

_[View the full topic](https://discuss.elastic.co/t/ml-watcher-configs/251696)._