# Why Kibana alerts are not consistent?

**URL:** https://discuss.elastic.co/t/why-kibana-alerts-are-not-consistent/223553
**Category:** Kibana
**Created:** [March 13, 2020, 5:50pm UTC](https://discuss.elastic.co/t/why-kibana-alerts-are-not-consistent/223553 "2020-03-13T17:50:36Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![rashmi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rashmi/32/16391_2.png) [@rashmi](https://discuss.elastic.co/u/rashmi)
#### Post date: [April 2, 2020, 11:15pm UTC](https://discuss.elastic.co/t/why-kibana-alerts-are-not-consistent/223553/5 "2020-04-02T23:15:21Z")

</div>

What happens when the watch triggers? can u plz capture the logs and compare it to the time when it does not trigger ?

Also alternatively, you may want to try instead then is the execute watch API, but with simulated action modes like this

```auto
POST _watcher/watch/my-watch/_execute
{
  "action_modes" : {
    "_all" : "simulate"
  }
}

```

Which executes your configured search, but will not execute the actions.. yet return useful info in the JSON response. Using the `alternative_input` with some scripting on the client side might be easier, to be honest.

Here is the link to similar question on testing a watch.: [How can Watchers be tested?](https://discuss.elastic.co/t/how-can-watchers-be-tested/65384/5)  
[https://www.elastic.co/blog/watching-the-watches-writing-debugging-and-testing-watches](https://www.elastic.co/blog/watching-the-watches-writing-debugging-and-testing-watches)

---

_[View the full topic](https://discuss.elastic.co/t/why-kibana-alerts-are-not-consistent/223553)._