# Scale monitoring using metricbeat

**URL:** https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891
**Category:** Beats
**Tags:** metricbeat
**Created:** [January 10, 2022, 1:05pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891 "2022-01-10T13:05:56Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![motkele](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@motkele](https://discuss.elastic.co/u/motkele)
#### Post date: [January 10, 2022, 1:05pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891/1 "2022-01-10T13:05:56Z")

</div>

Hello,

I have a very specific question regarding the way to collect metrics using metricbeat.  
I would like to collect the metrics from all the services running on the server (and for which a metricbeat module is available).  
I would like to better understand if Elastic provides some mechanism to perform an automatic discovery and config in that case:

- discover which services are running on the server on which the metricbeat agent is running
- configure elastic to start collecting metrics fron these services

Thanks,  
Moti.

---

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [January 10, 2022, 1:25pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891/2 "2022-01-10T13:25:17Z")

</div>

Hi @motkele !

This is not supported in the generic case but can be achieved in specific environments like docker, kubernetes etc. You can check [Autodiscover | Metricbeat Reference [7.16] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-autodiscover.html) to have an idea of what is supported there.

C.

---

<div class="post-metadata">

### Author: ![motkele](https://avatars.discourse-cdn.com/v4/letter/m/77aa72/32.png) [@motkele](https://discuss.elastic.co/u/motkele)
#### Post date: [January 10, 2022, 1:30pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891/3 "2022-01-10T13:30:28Z")

</div>

Hi Chris,  
Thanks a lot of the prompt response.  
What about VM based environments ?  
I assume that each and every metricbeat user deploying on several dozens of servers is encountering the same challenge since he/she would not like to start and discover the services running on each server and then configure each one of them in a manual manner.  
Moti.

---

<div class="post-metadata">

### Author: ![ChrsMark](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chrsmark/32/55858_2.png) [@ChrsMark](https://discuss.elastic.co/u/ChrsMark)
#### Post date: [January 10, 2022, 1:46pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891/4 "2022-01-10T13:46:04Z")

</div>

Yes I see the point here, hence the problem is too generic and there would be needed a mechanism to probe for known services' endpoints as well as a level of integration with each one of the orchestrators/hypervisors so as to automatically identify newcomer hosts.

---

<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: [February 7, 2022, 3:46pm UTC](https://discuss.elastic.co/t/scale-monitoring-using-metricbeat/293891/5 "2022-02-07T15:46:14Z")

</div>

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