# Data Pipeline Design Considerations

**URL:** <https://discuss.elastic.co/t/data-pipeline-design-considerations/322717>\
**Category:** Logstash\
**Created:** [January 9, 2023, 9:47am UTC](https://discuss.elastic.co/t/data-pipeline-design-considerations/322717 "2023-01-09T09:47:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Tiharqa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tiharqa/32/95336_2.png) [@Tiharqa](https://discuss.elastic.co/u/Tiharqa)\
**Post date:** [January 9, 2023, 9:47am UTC](https://discuss.elastic.co/t/data-pipeline-design-considerations/322717/1 "2023-01-09T09:47:21Z")

</div>

So I have a confluent kafka with multiple topics per network divided as follows

NET1: Data

NET1-SYSLG

NET1-WIN

======  
NET2 : Data

NET2-SYSLG

NET2-WIN

I have 2 logstash servers reading from those topics on Kafka

1 reading the topics from NET1 going to Elastic  
the second is reading only the topic data from NET2 also going to the same Elastic  
If i have created 2 spaces to isolate the data once I called it NET1 and the second one is NET2

NET1:SYSLG, WIN ---\> Logstash 1 -------------------- NET1 SPACE  
KFK- -------------------------------- ------- | --------\> ELASTIC |  
NET2: SYSLG, WIN --- \> Logstash2 --------------------- NET2 SPACE

what is best approach or procedures to write data for logstash 1 to SPACE 1 index called net1-syslog  
How do I go about configuring that on Elasticsearch to map those incoming events from each logstash to their corresponding space and indices ? Any insight or help would be appreciated

---

<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 6, 2023, 9:48am UTC](https://discuss.elastic.co/t/data-pipeline-design-considerations/322717/2 "2023-02-06T09:48:12Z")

</div>

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