# ELK - MetricBeat dataflow

**URL:** <https://discuss.elastic.co/t/elk-metricbeat-dataflow/218543>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [February 10, 2020, 8:38am UTC](https://discuss.elastic.co/t/elk-metricbeat-dataflow/218543 "2020-02-10T08:38:52Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![iniyan.g](https://avatars.discourse-cdn.com/v4/letter/i/87869e/32.png) [@iniyan.g](https://discuss.elastic.co/u/iniyan.g)\
**Post date:** [February 10, 2020, 8:38am UTC](https://discuss.elastic.co/t/elk-metricbeat-dataflow/218543/1 "2020-02-10T08:38:52Z")

</div>

Hi ELK Team

We are currently working on to setup instance/VM level monitoring using beats. We have chosen Metricbeat for pushing VM data to logstash and to elasticsearch. As of now, we are evaluating this only for 2 client machines in Azure. Then, we would like to enhance it to other VMs in different subscriptions. (~ over 200 VMs)

The ask is here that, how much data transfer (In KB, MB or GB) are expected for each VM to push data to logstash in every 10 or 15 minutes.

Note:\_ **strong text** We have configured Metricbeat to enable only system logs.

Thanks,  
Iniyan G

---

<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:** [March 9, 2020, 8:38am UTC](https://discuss.elastic.co/t/elk-metricbeat-dataflow/218543/2 "2020-03-09T08:38:54Z")

</div>

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