# Kibana and marvel- agent

**URL:** <https://discuss.elastic.co/t/kibana-and-marvel-agent/143503>\
**Category:** Kibana\
**Created:** [August 8, 2018, 12:03pm UTC](https://discuss.elastic.co/t/kibana-and-marvel-agent/143503 "2018-08-08T12:03:02Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![nareshm\_399](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nareshm_399/32/55066_2.png) [@nareshm\_399](https://discuss.elastic.co/u/nareshm_399)\
**Post date:** [August 8, 2018, 12:03pm UTC](https://discuss.elastic.co/t/kibana-and-marvel-agent/143503/1 "2018-08-08T12:03:02Z")

</div>

I have 17 node ES cluster, I have marvel-agent installed on all nodes. Should I install kibana on 17 nodes or any one of the node?

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [August 9, 2018, 2:16am UTC](https://discuss.elastic.co/t/kibana-and-marvel-agent/143503/2 "2018-08-09T02:16:39Z")

</div>

One generally accepted production practice is to install Kibana on an instance with an ES Coordinating node, meaning that it's NOT a master or data node. Kibana then points to the local ES instance which is aware of the ES cluster and can route to any available node.

---

<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 6, 2018, 2:16am UTC](https://discuss.elastic.co/t/kibana-and-marvel-agent/143503/3 "2018-09-06T02:16:42Z")

</div>

Closed on September 6, 2018, 2:16am UTC

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