# Missing event - file input plugin / NFS **URL:** https://discuss.elastic.co/t/missing-event-file-input-plugin-nfs/107838 **Category:** Logstash **Created:** [November 15, 2017, 11:19pm UTC](https://discuss.elastic.co/t/missing-event-file-input-plugin-nfs/107838 "2017-11-15T23:19:52Z") **Posts on this page:** 1 **Showing post:** 10
### Author: ![guyboertje](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/guyboertje/32/31592_2.png) [@guyboertje](https://discuss.elastic.co/u/guyboertje) #### Post date: [November 16, 2017, 3:37pm UTC](https://discuss.elastic.co/t/missing-event-file-input-plugin-nfs/107838/10 "2017-11-16T15:37:01Z")
I suggest filebeat because it the recommended tech now days. The LS file input has not had much attention in a long time. Both LS and Filebeat are OK to read a NFS mount - there some things to be aware of. > [@Using logstash File Input to monitor files on a network share](https://discuss.elastic.co/t/using-logstash-file-input-to-monitor-files-on-a-network-share/182/2): > > Reading files from network shares is OK with Logstash's file input. slight_smile One thing to be aware of: Some network filesystems (nfs) have aggressive client-side caching that cause Logstash to be lied to about the state of the file - this caching prevents Logstash from detecting new changes in files on those nfs mounts. For windows, Samba/CIFS I think, I can't recall anyone having trouble with this, so it should work fine. Of course, let us know if you find otherwise smile Also Jordan wrote this is in an internal memo: > My still-unclear understanding of this problem is follows: Reading and writing from the same file with two different NFS clients is not supported by NFS itself. Can you put filebeat on remote machine? --- _[View the full topic](https://discuss.elastic.co/t/missing-event-file-input-plugin-nfs/107838)._