# Ingesting CSV reports through Filebeat to Logstash

**URL:** <https://discuss.elastic.co/t/ingesting-csv-reports-through-filebeat-to-logstash/137680>\
**Category:** Logstash\
**Created:** [June 27, 2018, 6:52pm UTC](https://discuss.elastic.co/t/ingesting-csv-reports-through-filebeat-to-logstash/137680 "2018-06-27T18:52:56Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![joshua625](https://avatars.discourse-cdn.com/v4/letter/j/e99b99/32.png) [@joshua625](https://discuss.elastic.co/u/joshua625)\
**Post date:** [July 3, 2018, 8:41pm UTC](https://discuss.elastic.co/t/ingesting-csv-reports-through-filebeat-to-logstash/137680/24 "2018-07-03T20:41:59Z")

</div>

Well. the only thing why I am focusing on Filebeat is just for monitoring the beats and see if there are any events missing while ingesting to Logstash. If Filebeat doesn't parse csv, then I think I should definitely go with the input "file" to parse rather than debugging the errors.

---

<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 31, 2018, 8:42pm UTC](https://discuss.elastic.co/t/ingesting-csv-reports-through-filebeat-to-logstash/137680/25 "2018-07-31T20:42:02Z")

</div>

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

[Previous page](https://discuss.elastic.co/t/ingesting-csv-reports-through-filebeat-to-logstash/137680.md?page=1)