# Logstash integration with another ETL pipeline

**URL:** <https://discuss.elastic.co/t/logstash-integration-with-another-etl-pipeline/149408>\
**Category:** Logstash\
**Created:** [September 21, 2018, 7:24am UTC](https://discuss.elastic.co/t/logstash-integration-with-another-etl-pipeline/149408 "2018-09-21T07:24:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fenster25](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fenster25/32/55546_2.png) [@fenster25](https://discuss.elastic.co/u/fenster25)\
**Post date:** [September 21, 2018, 7:24am UTC](https://discuss.elastic.co/t/logstash-integration-with-another-etl-pipeline/149408/1 "2018-09-21T07:24:01Z")

</div>

Hi,

I am working on a project similar to [https://github.com/compose/transporter](https://github.com/compose/transporter) but with more support for other high-level data sources like MySQL, Redis, firestore etc

I was looking for a way to integrate this with logstash, in which my project would act like an input which will provide logstash with the data collected from all these high-level data sources all at once and then transfer that to logstash to be indexed onto ES

I wanted to know whether this sounds like a good use case or not?

One advantage I can think of is users will only have to set a configuration for this plugin instead of all the other data sources individually.

---

<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:** [October 19, 2018, 7:24am UTC](https://discuss.elastic.co/t/logstash-integration-with-another-etl-pipeline/149408/2 "2018-10-19T07:24:02Z")

</div>

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