# Kibana/Marvel Monitoring

**URL:** <https://discuss.elastic.co/t/kibana-marvel-monitoring/98064>\
**Category:** Kibana\
**Created:** [August 23, 2017, 11:59am UTC](https://discuss.elastic.co/t/kibana-marvel-monitoring/98064 "2017-08-23T11:59:09Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Cen\_giz](https://avatars.discourse-cdn.com/v4/letter/c/839c29/32.png) [@Cen\_giz](https://discuss.elastic.co/u/Cen_giz)\
**Post date:** [August 23, 2017, 11:59am UTC](https://discuss.elastic.co/t/kibana-marvel-monitoring/98064/1 "2017-08-23T11:59:09Z")

</div>

Hi,

Planning to setup enterprise monitoring tool to check the health of Kibana and Marvel both (health of Elastic clusters configured in Marvel as well)

What is the best method to do this?

Thx,  
Cengiz

---

<div class="post-metadata">

**Author:** ![Joe\_Fleming](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joe_fleming/32/3561_2.png) [@Joe\_Fleming](https://discuss.elastic.co/u/Joe_Fleming)\
**Post date:** [August 23, 2017, 5:47pm UTC](https://discuss.elastic.co/t/kibana-marvel-monitoring/98064/2 "2017-08-23T17:47:07Z")

</div>

I don't think I follow. Monitoring (formerly Marvel) already monitors Elasticsearch and Kibana, and effectively monitors itself as a result.

---

<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:** [September 20, 2017, 5:47pm UTC](https://discuss.elastic.co/t/kibana-marvel-monitoring/98064/3 "2017-09-20T17:47:21Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.