Hey,
A unique identifier for this filestream input. Each filestream input must have a unique ID. Filestream will not start inputs with duplicated IDs.
What's the scope of the id? Global in ES? Local to the backing index/datastream Filebeat feeds into? Local to the Filebeat instance using the configuration file? Just so that I know how "unique" it needs to be.
Side note:
The
containerinput is just a preset for theloginput. Theloginput is deprecated in version 7.16 and it's disabled by default in version 9.0.
That's from the filestream migration guide for the 9.0x series link
I only found mentions of the log input being deprecated in the 8.x series, as shown here, with no additional mention for the 8.x0 container input
Any reason for not discouraging readers from using the container input in the previous version? Docker logs harvesting with Filebeat is going to be widespread in our environment. We've just postponed our production roll-out due to external factors. Feels like I dodged a bullet thanks to sheer luck here. As a self-hosting user for now, I'm absolutely not entitled to anything, but I think this is an example of a needlessly frustrating surprise.