The idea is not to do a heavy parsing,
but create a utility to include dynamic field values,
relative to an individual log file. (./hostname is beside the log file)
These file can then be dynamically generated by other programs subsequently.
Or in this case docker itself [the main reason why i want this] =)
Looks close. Because in the docker example i given, it is possible to derive the hostname unique to each log file name, which can be passed in"Dynamic lookup processing scripts".
On the positive side, it is a lot more comprehensive and versatile solution. On the negative side, with the user permission safety, etc. It can be a lot harder to setup.
As for reloading of config, because each log file will have an individual field value unique to them. This will probably need a "FileBeatConfigBeat" to generate individual prospectors with field values for each log file.
How is the hostname file generated? I assume this is already generated by some script, so this script could directly create the prospector config file.
The hostname file is generated by docker itself in this case. So not much option in modifying that.
However since it is possible to scan for docker system structure, yup. Some bash script writing is probably needed, see how it goes. I may give it a try =)
Which version is prospector reloading in? and how do I trigger it?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.