# Elasticsearch and metricbeat

**URL:** https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340
**Category:** Beats
**Tags:** metricbeat
**Created:** [May 13, 2024, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340 "2024-05-13T05:56:45Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Sarfaraz\_Shaikh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarfaraz_shaikh/32/134413_2.png) [@Sarfaraz\_Shaikh](https://discuss.elastic.co/u/Sarfaraz_Shaikh)
#### Post date: [May 13, 2024, 5:56am UTC](https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340/1 "2024-05-13T05:56:45Z")

</div>

I need help to know the server specs to collect metrics from 1000 client server. How we can setup.

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [May 13, 2024, 11:17am UTC](https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340/2 "2024-05-13T11:17:57Z")

</div>

I believe the easiest way is to use the [Elastic Agent](https://www.elastic.co/elastic-agent) and then deploy agent policies to do whatever you need.

---

<div class="post-metadata">

### Author: ![Sarfaraz\_Shaikh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sarfaraz_shaikh/32/134413_2.png) [@Sarfaraz\_Shaikh](https://discuss.elastic.co/u/Sarfaraz_Shaikh)
#### Post date: [May 13, 2024, 12:14pm UTC](https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340/3 "2024-05-13T12:14:08Z")

</div>

What will be the server configuration required for it. One cluster is enough for that

---

<div class="post-metadata">

### Author: ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [May 13, 2024, 12:50pm UTC](https://discuss.elastic.co/t/elasticsearch-and-metricbeat/359340/4 "2024-05-13T12:50:32Z")

</div>

There are many factors involved like:

- retention days
- using searchable snapshots (needs a commercial license) to reduce the number of nodes and use storage instead
- running on cloud, using our serverless offer
- number of events collected per machine...

One of the nice thing with Elastic is the elasticity part, so it can scale out if needed.

But one of the way to get actual numbers is to test with some days of data on some machines and then multiply by a factor. Something you can easily do from [cloud.elastic.co](http://cloud.elastic.co).
