# I cannot index "status.actions.my\_webhook.last\_execution.successful" in .watcher-history-\* **URL:** \ **Category:** Kibana\ **Created:** [June 22, 2018, 2:28pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038 "2018-06-22T14:28:10Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Piotr\_Pawlak](https://avatars.discourse-cdn.com/v4/letter/p/dc4da7/32.png) [@Piotr\_Pawlak](https://discuss.elastic.co/u/Piotr_Pawlak)\ **Post date:** [June 22, 2018, 2:28pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/1 "2018-06-22T14:28:10Z")
Hi there, I am trying setup a watcher to send an alert based on a field status.actions.my\_webhook.last\_execution.successful": "false" that can be found in .watcher-history-\*. This is to notify us if our 3rd parties notification API endpoint changed/not available. Currently I am having a problem to index that field so it is searchable. I tried to refresh the fields list and gone up from ~130 to 170 but the field is still not showing there. Any help or guidance on this would be appreciated. ---
**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\ **Post date:** [June 22, 2018, 2:58pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/2 "2018-06-22T14:58:14Z")
Hi @Piotr_Pawlak, Are you using the Threshold Alert UI to create this? You won't be able to use that for creating this watch as the mappings for `.watcher-history-*` aren't structured enough to allow you dive into the status of actions. ---
**Author:** ![Piotr\_Pawlak](https://avatars.discourse-cdn.com/v4/letter/p/dc4da7/32.png) [@Piotr\_Pawlak](https://discuss.elastic.co/u/Piotr_Pawlak)\ **Post date:** [June 22, 2018, 3:34pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/3 "2018-06-22T15:34:43Z")
this is related [Alert when watcher is in error state - .watcher\_history](https://discuss.elastic.co/t/alert-when-watcher-is-in-error-state-watcher-history/136348/3) topic I raised a few days ago. All I am looking for is a programmatic method of getting alerted if a watcher is in error state. At the moment I found a field that is changing when a watcher error happen so I am trying to come up with a query first before creating an alert. ---
**Author:** ![chrisronline](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrisronline/32/28230_2.png) [@chrisronline](https://discuss.elastic.co/u/chrisronline)\ **Post date:** [June 22, 2018, 4:03pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/4 "2018-06-22T16:03:38Z")
Your best bet is to create a watch against the `.watcher-history-*` indices. In the query part, do a `match_all` to grab all the watches (or you can filter into a subset based on your needs). You cannot write a query that will filter on status because the `status` field is not indexed. In the condition part, investigate the `status.actions.my_webhook.last_execution.successful` part of the response. ---
**Author:** ![Piotr\_Pawlak](https://avatars.discourse-cdn.com/v4/letter/p/dc4da7/32.png) [@Piotr\_Pawlak](https://discuss.elastic.co/u/Piotr_Pawlak)\ **Post date:** [June 25, 2018, 2:59pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/5 "2018-06-25T14:59:14Z")
Thanks I will investigate this solution and see how far i will get. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 23, 2018, 2:59pm UTC](https://discuss.elastic.co/t/i-cannot-index-status-actions-my-webhook-last-execution-successful-in-watcher-history/137038/6 "2018-07-23T14:59:23Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.