# Question about Watcher ( Xpack-Alerts)

**URL:** <https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-alerting\
**Created:** [October 19, 2016, 7:39pm UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436 "2016-10-19T19:39:17Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![uraees](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uraees/32/12600_2.png) [@uraees](https://discuss.elastic.co/u/uraees)\
**Post date:** [October 19, 2016, 7:39pm UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436/1 "2016-10-19T19:39:17Z")

</div>

Can Watcher be used to watch other enterprise entities other than elastic stack. For example polling to some table for some status change and alert based on that ? Or is it solely designed to look into elastic stack?

Thanks  
Raees

---

<div class="post-metadata">

**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:** [October 19, 2016, 9:06pm UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436/2 "2016-10-19T21:06:19Z")

</div>

It's only designed for ES.

---

<div class="post-metadata">

**Author:** ![spinscale](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/spinscale/32/25011_2.png) [@spinscale](https://discuss.elastic.co/u/spinscale)\
**Post date:** [October 20, 2016, 7:41am UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436/3 "2016-10-20T07:41:42Z")

</div>

Hey,

If your application is able to send HTTP requests, you could use the logstash HTTP input to index data into Elasticsearch and use watcher on top of that.

If your application has its own HTTP interface, you could use the HTTP input directly.

Watcher itself has no other means of peeking into other applications, it requires a push or pull architecture, where the other application is able to expose information about itself.

--Alex

---

<div class="post-metadata">

**Author:** ![uraees](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/uraees/32/12600_2.png) [@uraees](https://discuss.elastic.co/u/uraees)\
**Post date:** [October 20, 2016, 2:12pm UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436/4 "2016-10-20T14:12:20Z")

</div>

Thanks , this was what I was looking for

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 1:42pm UTC](https://discuss.elastic.co/t/question-about-watcher-xpack-alerts/63436/5 "2017-07-06T13:42:26Z")

</div>


