Currently AnaLog is able to scan a specified directory for files to list them as choice options in the UI choices list. This is mainly to simplify AnaLog use for the rotating log files.
Such scanning would also be useful for both Docker and Kubernetes resources as they often have dynamic (generally unpredictable) names. For Kubernetes, it can become the first step toward #25 solution since the scanning may substantially simplify the way users describe the composite log entries.
The syntax of the scanning entries in the config file should be aligned with the one already employed for the files scanning.
Currently AnaLog is able to scan a specified directory for files to list them as choice options in the UI choices list. This is mainly to simplify AnaLog use for the rotating log files.
Such scanning would also be useful for both Docker and Kubernetes resources as they often have dynamic (generally unpredictable) names. For Kubernetes, it can become the first step toward #25 solution since the scanning may substantially simplify the way users describe the composite log entries.
The syntax of the scanning entries in the config file should be aligned with the one already employed for the files scanning.