# The best way to collect custom data?

**URL:** <https://discuss.elastic.co/t/the-best-way-to-collect-custom-data/180230>\
**Category:** Beats\
**Created:** [May 8, 2019, 6:14pm UTC](https://discuss.elastic.co/t/the-best-way-to-collect-custom-data/180230 "2019-05-08T18:14:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Todd\_Sayers](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/todd_sayers/32/45838_2.png) [@Todd\_Sayers](https://discuss.elastic.co/u/Todd_Sayers)\
**Post date:** [May 8, 2019, 6:14pm UTC](https://discuss.elastic.co/t/the-best-way-to-collect-custom-data/180230/1 "2019-05-08T18:14:15Z")

</div>

I'd like to know the "correct" or "best" way to get custom metrics (e.g., Lustre performance, OPA topology, etc) into ES using the Beats "system." My first thought was to create a Metricbeat module. I've also seen Execbeat mentioned.

Were I able to just have a beat send the STDOUT of a Python script to ES, that would be great. I doubt that it's that simple (this is what I do with Telegraf).

Ultimately, I'd prefer to have one daemon (e.g., Metricbeat) to rule all of the metrics collection. I work in Linux HPC (we don't have, need, or want WIndows). Thanks!

---

<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:** [June 5, 2019, 8:14pm UTC](https://discuss.elastic.co/t/the-best-way-to-collect-custom-data/180230/2 "2019-06-05T20:14:49Z")

</div>

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