Filebeat network shares support

[kvch]

The log input of Filebeat does not support reading files from network shares and cloud providers. There are two main issues that have to be addressed before we are ready.

• Identifying files Identity tracking of files in Filebeat inputs #13492
  Filebeat identifies files based on inode and device ids. However, these two numbers might change from time to time when the files are located on a network share. Thus, Filebeat cannot tell apart files correctly. Users might end up with duplicated data as Filebeat believes it has found a new file and rereads whole content.
• Reading from files occasionally return null
  The offset returned from file readers are sometimes incorrect. Filebeat needs to check if the return bytes sequence is nil. If yes, it needs to revert back to the end of the file, as it has tried to read from an invalid area. A possible solution is described in this comment: Add initial support for configurable file identity tracking #18748 (comment)

[elasticmachine]

Pinging @elastic/integrations-services (Team:Services)

[kvch]

CC @urso

[botelastic]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[elasticmachine]

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

[botelastic]

Hi!
We just realized that we haven't looked into this issue in a while. We're sorry!

We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1.
Thank you for your contribution!