# Why log comming from filebeat are automaticaly parsed with output elastic and not with logstash

**URL:** <https://discuss.elastic.co/t/why-log-comming-from-filebeat-are-automaticaly-parsed-with-output-elastic-and-not-with-logstash/137619>\
**Category:** Logstash\
**Created:** [June 27, 2018, 12:50pm UTC](https://discuss.elastic.co/t/why-log-comming-from-filebeat-are-automaticaly-parsed-with-output-elastic-and-not-with-logstash/137619 "2018-06-27T12:50:12Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![artonge](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/artonge/32/29371_2.png) [@artonge](https://discuss.elastic.co/u/artonge)\
**Post date:** [June 27, 2018, 12:50pm UTC](https://discuss.elastic.co/t/why-log-comming-from-filebeat-are-automaticaly-parsed-with-output-elastic-and-not-with-logstash/137619/1 "2018-06-27T12:50:12Z")

</div>

Hi,

When I set the output to elastic in my filebeat config, all the logs from modules like apache2 are automatically parsed but when I send them to logstash, they are not.

- Is this a wanted behaviour ?
- Couldn't they be automatically parsed when sent to logstash ?
- Who is parsing them when sending them to elastic, elastic or filebeat ?
- Is it possible to have two output when running a single instance of filebeat ?

Louis

---

<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:** [July 25, 2018, 12:57pm UTC](https://discuss.elastic.co/t/why-log-comming-from-filebeat-are-automaticaly-parsed-with-output-elastic-and-not-with-logstash/137619/2 "2018-07-25T12:57:13Z")

</div>

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