# Filebeat v/s Logstash file Path
**URL:** https://discuss.elastic.co/t/filebeat-v-s-logstash-file-path/90149
**Category:** Logstash
**Created:** [June 20, 2017, 7:20pm UTC](https://discuss.elastic.co/t/filebeat-v-s-logstash-file-path/90149 "2017-06-20T19:20:42Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@vgupta0308](https://discuss.elastic.co/u/vgupta0308)
#### Post date: [June 20, 2017, 7:20pm UTC](https://discuss.elastic.co/t/filebeat-v-s-logstash-file-path/90149/1 "2017-06-20T19:20:42Z")
Hi,
During reading the posts, I have found most of the people are using filebeat even we can input the file path for parsing the logs. Can anyone please explain the difference in between both options? What are the pros and crons?
Would filebeat process the logs fast as it sends the logs directly to the port for processing the logs via Logstash?
Thanks,
Vinay Gupta
---
### Author:  [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)
#### Post date: [June 21, 2017, 5:37am UTC](https://discuss.elastic.co/t/filebeat-v-s-logstash-file-path/90149/2 "2017-06-21T05:37:37Z")
The main point of Filebeat is the lower resource overhead, but in terms of disk space required for installation but also the RAM overhead.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 19, 2017, 5:37am UTC](https://discuss.elastic.co/t/filebeat-v-s-logstash-file-path/90149/3 "2017-07-19T05:37:45Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.