The same message has been popping up for a while now: it would be really handy if an existing ELK setup could be moved to the cloud, and part of this is of course porting the file plugin to s3 (or am I missing another option?).
This process appears rather straightforward if you are watching a single file, yet having a "path" (as it is called in the file plugin) with wildcards, such as this, doesn't appear to be supported.
path => "d:/elasticdata/**/server.log*"
Is this a planned future feature? Or are there technical limitations that I should be aware of (which prevent this)?
PS: I certainly hope this will not become the next "closed after 28 days of inactivity" message on exactly the same topic...