# Metricbeat data source

**URL:** <https://discuss.elastic.co/t/metricbeat-data-source/127683>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [April 11, 2018, 5:08pm UTC](https://discuss.elastic.co/t/metricbeat-data-source/127683 "2018-04-11T17:08:34Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alex\_Mendez](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@Alex\_Mendez](https://discuss.elastic.co/u/Alex_Mendez)\
**Post date:** [April 11, 2018, 5:08pm UTC](https://discuss.elastic.co/t/metricbeat-data-source/127683/1 "2018-04-11T17:08:34Z")

</div>

Is there a way to pull metric beat data from a single source for many servers, example syslog, filebeat style?

thanks

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [April 13, 2018, 1:58pm UTC](https://discuss.elastic.co/t/metricbeat-data-source/127683/2 "2018-04-13T13:58:42Z")

</div>

It's not 100% clear to me what you are asking. What is it that you are trying to accomplish?

You could have all Metricbeat instances push data to a queue like redis or kafka, then pull data from that queue. This is a common deployment setup. Then use Logstash to process data off the queue and route it to ES and other destinations.

---

<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 11, 2018, 1:59pm UTC](https://discuss.elastic.co/t/metricbeat-data-source/127683/3 "2018-05-11T13:59:01Z")

</div>

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