A very common use case for TIBCO LogLogic Universal Collector is to collect data from several (local) subfolders as follows:

C:\UCTest\app1\app1.log
C:\UCTest\app2\app2.log
C:\UCTest\app3\app3.log
…
…
…

To achieve this, users have to create as many Real Time configurations as paths they have to collect from.  Also, up to current TIBCO LogLogic Universal Collector version (by the time of this writing is 2.8 HF2), there is no feature for Real Time collection to allow users to configure subfolders using wildcards.
Starting from TIBCO LogLogic Universal Collector 2.8 - Remote File collection allows customers to use wildcards on subfolders and filenames. But what if users need this for a local collection?

As its name suggests, Remote File collection is meant to collect data from a remote server. However, when protocol is set to 'file', it is possible to set the path locally and use wildcards so that users need just one Remote File configuration to collect data from a scenario like the one given in details.

To do so, configure Remote File collection as shown below:

There is - however - a couple of downsides to this solution. Firstly, the minimum collection frequency is 5 minutes. Also, when users select 'File' rather than 'Directory' an option to configure "File Rotation" and "File change notification" is available.

If actual real time is not needed and there is no file rotation or file change notification required then this is the best choice at the moment.