# Configuring filebeat logstash plugin to transform one log, but not another

**URL:** <https://discuss.elastic.co/t/configuring-filebeat-logstash-plugin-to-transform-one-log-but-not-another/160945>\
**Category:** Logstash\
**Created:** [December 14, 2018, 4:53pm UTC](https://discuss.elastic.co/t/configuring-filebeat-logstash-plugin-to-transform-one-log-but-not-another/160945 "2018-12-14T16:53:47Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![Ryan\_Downey](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ryan_downey/32/35987_2.png) [@Ryan\_Downey](https://discuss.elastic.co/u/Ryan_Downey)\
**Post date:** [December 14, 2018, 8:20pm UTC](https://discuss.elastic.co/t/configuring-filebeat-logstash-plugin-to-transform-one-log-but-not-another/160945/5 "2018-12-14T20:20:54Z")

</div>

I may be misunderstanding you but is this what you're looking to do:

> [@Can I filter the Output data separately?!](https://discuss.elastic.co/t/can-i-filter-the-output-data-separately/36064):
>
> We have the following env: LS 2.0.x; ES 2.0.x and K 4.2.x The input comes from the trace logs that an application produces, we filter the data and then wish to populate two separate (but related) indices: orders and orders\_alt. Each one of these has a separate mapping structure of data. We are having trouble controlling what fields go with what Index. We end up with the same fields in both Indices because ES creates them dynamically and we have to way to filter between the Outputs. How c…

---

_[View the full topic](https://discuss.elastic.co/t/configuring-filebeat-logstash-plugin-to-transform-one-log-but-not-another/160945)._
