# Full Stack

**URL:** https://discuss.elastic.co/t/full-stack/178052
**Category:** Beats
**Tags:** metricbeat
**Created:** [April 23, 2019, 2:17pm UTC](https://discuss.elastic.co/t/full-stack/178052 "2019-04-23T14:17:17Z")
**Posts on this page:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![Masdi](https://avatars.discourse-cdn.com/v4/letter/m/87869e/32.png) [@Masdi](https://discuss.elastic.co/u/Masdi)
#### Post date: [April 23, 2019, 2:17pm UTC](https://discuss.elastic.co/t/full-stack/178052/1 "2019-04-23T14:17:17Z")

</div>

Hi, I was wondering why this full stack is not appropriate in production: [https://www.elastic.co/fr/blog/a-full-stack-in-one-command](https://www.elastic.co/fr/blog/a-full-stack-in-one-command)

I'd like to setup a K8s/Kafka/ELK cluster and monitor it with Metricbeat.

---

<div class="post-metadata">

### Author: ![ruflin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ruflin/32/3116_2.png) [@ruflin](https://discuss.elastic.co/u/ruflin)
#### Post date: [April 26, 2019, 9:03am UTC](https://discuss.elastic.co/t/full-stack/178052/2 "2019-04-26T09:03:20Z")

</div>

This is a very simple setup for Elasticsearch. If you want to take this into production you should think about how much masters, nodes etc. you need.

---

<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: [May 24, 2019, 9:18am UTC](https://discuss.elastic.co/t/full-stack/178052/3 "2019-05-24T09:18:31Z")

</div>

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