# Es document count != wc -l output of file after sending data with logstash?
**URL:** https://discuss.elastic.co/t/es-document-count-wc-l-output-of-file-after-sending-data-with-logstash/304293
**Category:** Logstash
**Created:** [May 9, 2022, 8:29pm UTC](https://discuss.elastic.co/t/es-document-count-wc-l-output-of-file-after-sending-data-with-logstash/304293 "2022-05-09T20:29:08Z")
**Posts on this page:** 2
**Page:** 2
### Author:  [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)
#### Post date: [May 17, 2022, 9:19pm UTC](https://discuss.elastic.co/t/es-document-count-wc-l-output-of-file-after-sending-data-with-logstash/304293/21 "2022-05-17T21:19:47Z")
Both Filebeat and Logstash are reliable, and they both will retry to send logs in the case of some communication error with Elasticsearch, this can in some cases lead to duplicate documents and there are ways to deal with date.
As already said your issue is specific to your case and your data, but without seeing your data and trying to replicate it is not possible to know what is the issue and how to fix it.
As asked:
> [@leandrojmp](#):
>
> Does this happen with every csv file? How this csv file is created? Can you provide a sample of the file where this issue happens?
Can you share a sample of your file with any private information redacted so someone can try to replicate your issue?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 14, 2022, 9:20pm UTC](https://discuss.elastic.co/t/es-document-count-wc-l-output-of-file-after-sending-data-with-logstash/304293/22 "2022-06-14T21:20:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
[Previous page](https://discuss.elastic.co/t/es-document-count-wc-l-output-of-file-after-sending-data-with-logstash/304293.md?page=1)