# Alerting on crushed cluster

**URL:** https://discuss.elastic.co/t/alerting-on-crushed-cluster/999
**Category:** Elasticsearch
**Tags:** elastic-stack-alerting
**Created:** [May 20, 2015, 4:56pm UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999 "2015-05-20T16:56:02Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![tzachi](https://avatars.discourse-cdn.com/v4/letter/t/e9bcb4/32.png) [@tzachi](https://discuss.elastic.co/u/tzachi)
#### Post date: [May 20, 2015, 4:56pm UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999/1 "2015-05-20T16:56:02Z")

</div>

Let's say that the production cluster crushed and not responding to searches or http queries initiated by watcher, will this fact trigger an alert?

---

<div class="post-metadata">

### Author: ![mvg](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mvg/32/98890_2.png) [@mvg](https://discuss.elastic.co/u/mvg)
#### Post date: [May 20, 2015, 8:59pm UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999/2 "2015-05-20T20:59:41Z")

</div>

If you install Watcher in a separate cluster (can just be a single node cluster), you can detect via a Watch if your production cluster crashed.

---

<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: [May 20, 2015, 11:17pm UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999/3 "2015-05-20T23:17:42Z")

</div>

If you are using Marvel in production we recommend that you send all that data from your nodes [to a separate cluster](https://www.elastic.co/guide/en/marvel/current/_installation.html#_installing_a_secondary_monitoring_cluster) (can be a small one).

It'd definitely then make sense to install Watcher on that same cluster and add these sorts of Watches to that instance.

---

<div class="post-metadata">

### Author: ![skearns](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skearns/32/125945_2.png) [@skearns](https://discuss.elastic.co/u/skearns)
#### Post date: [May 21, 2015, 9:21am UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999/4 "2015-05-21T09:21:31Z")

</div>

In addition to what mvg and warkolm mentioned, we do expect quite a few people to use Watcher to monitor Elasticsearch health and proactively notify the administrator if issues occur.

Today, Marvel is a great way to monitor Elasticsearch over time - it tracks many cluster health and performance metrics over time. We are planning a tighter integration between Marvel and Watcher over time, but for now, we have started providing recipes for creating watches based on Marvel data:  
[https://www.elastic.co/guide/en/watcher/current/watching-marvel-data.html](https://www.elastic.co/guide/en/watcher/current/watching-marvel-data.html)

---

<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:50pm UTC](https://discuss.elastic.co/t/alerting-on-crushed-cluster/999/5 "2017-07-06T13:50:02Z")

</div>


